Languages Around the World

home *** CD-ROM | disk | FTP | other *** search

/ Languages Around the World / LanguageWorld.iso / translat / babylon / demo-eng.voc < prev next >

Wrap

Text File | 1992-09-29 | 44.2 KB | 1,321 lines

STYLEman SYSTEM ADMINISTRATION GUIDE 3:00 INTRODUCTION TO PROCEDURES CONTENTS 3:10 SECURITY 3:10:10 Introduction 3:10:20 Company Details 3:10:21 Operator Master 3:10:22 Menu File 3:10:23 Program File 3:10:24 Field File 3:10:25 Security Level 3:10:26 Security Range 3:10:30 Security Profile 3:10:40 Security Violation 3:10:50 System Monitor 3:20 TRANSLATION 3:20:10 Introduction 3:20:20 Program Title Translation 3:20:21 Menu Title Translation 3:20:22 Message Translation 3:20:23 Help Text Translation 3:20:24 System Control File Parameter Translation 3:30 REBUILDS/BATCH OPERATIONS 3:30:10 Introduction 3:40 ARCHIVE ROUTINES 3:40:10 Introduction 3:50 COMPANY SET UP 3:50:10 Introduction 3:50:20 System Calendar 3:50:30 System Control File (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE 3:60 BACKGROUND DETAILS 3:60:10 Introduction 3:60:20 System Control File Parameters 3:60:30 Help Text 3:60:40 Indexed Help File 3:60:50 Message File 3:70 GENERAL ADMINISTRATION 3:70:10 Introduction (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE 3:10:10 Introduction STYLEman takes Security seriously allowing many differing types and differing methods of establishing security levels each capable of being used in conjunction with each other or used in part. Security is undertaken through a series of levels as follows: ┌────────> Enter OPERATOR ID and PASSWORD │ │ │ No V └─────── Is Operator Id and Password Valid? │ │ Yes V ┌────────────────> MENU │ │ │ V │ Enter PROGRAM Option │ │ │ V │ No Does Operator have Security └─────── Level to access program? │ │ Yes V ┌──────┬────────────> FIELD SECURITY <───────────────┬───┐ │ │ │ │ │ │ │ V │ │ │ │ No Does Operator have Security │ │ │ └─────── Level to access the field? │ │ │ │ │ │ │ │ Yes │ │ │ V │ │ │ Does Operator have Security No │ │ │ Level to Update the field? ──────────┘ │ │ │ │ │ │ Yes │ │ V │ │ FIELD RANGE │ │ │ │ │ V │ │ Does Operator have authority No │ │ to access code entered? ────────────────┘ │ │ │ │ Yes │ V │ Next Process Transaction └───────────────────────────┘ Field (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE The level of security that you maintain within STYLEman will very much depend upon the size of organisation you are, the number of users on the system and the diversity of the jobs they undertake and hence their requirements within STYLEman. The whole topic of security levels should be seriously considered prior to entering data into the "live" system. A member of Option Systems will be pleased to assist you in this decision making process. 3:10:20 Company Details STYLEman is a multi-company system enabling you to operate several companies independently within the system within the same database. There may be several reasons for doing this: - different trading companies within the main company which you wish to keep separate for reporting purposes. - different trading divisions that you wish to keep separate for reporting purposes The Company details maintain the current trading address of the "Company", telephone and fax numbers as well as details of the Registered Address, Bank Account, Registration numbers etc. as applicable. When you establish your Operator Ids you can restrict the Operators to individual companies or allow access to all, or selected companies. 3:10:21 Operator Master To be able to access the system, at all, each operator or group of operators must be assigned an Operator Id and an associated password. This ensures that only those personnel that you deem require access to the system actually can gain access. The Operator Id is also used to determine the use of the remainder of the security functions which operate throughout STYLEman. Established within each Operator Id is: - Whether or not that operator is allowed access to one Company only on the database, a selection or all of them. - The "home" menu of the operator, ie the menu first displayed when the operator signs on. This may be the Main menu as set up within STYLEman when delivered, or one of the established subsidiary menus (which encompasses the functions of the operator) or it may be a user-defined menu set up specifically for that operator or group of operators. - The Security level, which is used by the program and field level security to determine whether access should be granted or not. - The Operator Id also holds Language code, default printer and Time Difference details. (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE 3:10:22 Menu File To encourage rapid navigation around the system and the speed by which programs can be selected STYLEman utilises a menu structure methodology which allows you to move more conveniently around the system. There are predominantly two types of menu: - Main Menu This is the first menu accessed within the system and only contains the options to access other menus. It will not include program options. - Subsidiary This constitutes a second level menu where the options available are either programs or further levels of the menu structure. The subsidiary menu groups together those programs which constitute a functional area or part of a functional area within the system. STYLEman allows you to utilise the existing menu structure and use the security facilities within the system to restrict or deny access to programs. Alternatively you can establish user-defined menus which contains only those functions which an operator is likely to require. 3:10:23 Program File STYLEman allows you to assign to each program or those of your choosing a security level in keeping with the commercial sensitivity you place on the function of the program. The security levels operate between 00 and 99 with 00 being the lowest security level. The value assigned to the respective programs will differ from company to company dependent upon the users of the system and the degree of sensitivity placed upon certain elements of data. Each Operator Id when it is established within STYLEman is assigned a security level. This may be assigned dependent upon the seniority of the operator or on a "need to know information" or "need to perform function" basis. When the operator selects a program from the menu STYLEman compares the security level assigned to the program with that assigned to the Operator Id, to see if the operator has an equal or greater security level. If the security level is lower access will be denied, if it is equal to or greater the operator will be allowed to perform the selected function. 3:10:24 Field File Besides being able to prevent an operator from accessing a particular program because their security level is not high enough, you can also restrict access to view and update particular fields. (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE The Field File allows you to define to the system those fields which you wish to be able to set security against. This form of security is not available on every field as this would be an enormous task to establish, so STYLEman has restricted this form of security to fields which may contain sensitive information. The actual process of the various types of field security are discussed below. 3:10:25 Security Level There may be situations where it is not practical to prevent an operator from accessing a program altogether, (they may require it to complete their normal job) but whilst they are in the program there are certain fields which you do not wish them to see the contents of or you do not wish them to be able to change and then update the contents In the same way that STYLEman allows you to assign a security level to a program so the same can be undertaken for individual fields. For certain sensitive fields (eg Selling price in Order Entry) within STYLEman you have the facility to set security levels that must be exceeded firstly to view the contents of the field and secondly to be able to change and update the contents of the field. This allows the operator to enter a program, complete the task required and exit without seeing or influencing the contents of the sensitive fields. 3:10:26 Security Range Field range security enables you to allow an operator to access a field and update its contents but you can restrict them to specific values. For example, in your Credit Control department you may have several clerks each responsible for their own batch of accounts. Using the Field Range security you can set up either 40 individual valid account codes that the individual clerk can access or up to 20 ranges of account codes. This enables you to ensure that a clerk can influence their own accounts without being able to influence accounts for which they are not responsible. Through careful coding of your account numbers (see Section 6 of the STYLEman Implementation Guide) it is possible to significantly reduce the work content involved in setting up the security levels. Careful batching of accounts can make range selection very easy. (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE 3:10:30 Security Profile Once you have gone through the process of setting up the security levels within the system STYLEman enables you to produce a report which identifies the security profile that you have allocated to each operator. The report details the information established against the Operator Id, especially the security level, details each of the programs which can be called from a menu and displays their associated security level, identifies the field security for updating and viewing and any range restrictions that may be in place. This will provide both the System Administrator and the respective operator with the full details of their security standing. This can then be used to review and check at any stage if deemed applicable. 3:10:40 Security Violation Having established the security standards within the system it is also important that the System Administrator can determine if operators are trying to access functions for which they do not have authority. To aid the System Administrator in this task STYLEman provides a Security Violation display. This details any occasions where an operator has tried to access a function for which they do not have the respective authority. The display details the operator that attempted the access, the program effected and the date and time of the violation. From this display the System Administrator can check to make sure that operators are not constantly trying to access the same program for which they do not have the authority. This may well be a prompter to retraining of operators as to where functions can be found or to review the security levels established if it is found that an operator should have that facility. 3:10:50 System Monitor To enable the System Administrator to monitor the activity of the users of the system STYLEman provides a System Monitor which shows the details of each user, the program they are currently in and the date and time that they started. This allows the Administrator to potentially identify where users have left a screen on in a function etc. (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE 3:20 TRANSLATION 3:20:10 Introduction STYLEman is designed to be a multi-lingual package enabling two users in different countries, using different languages to be able to access the same data regardless. All the text supplied with the system is in English and STYLEman provides you with the facility to translate all relevant text to the required language. Areas that are covered by translation include: Display Text Report Text Error and warning message text Menu text Program Titles Help Text System Control File Parameters Text The advantage this has is that it allows you to include national, regional or company terminology into the translation therefore making it much more personalised than a standard classical translation. 3:20:20 Program Title Translation Each program within the STYLEman system has assigned to it a 25 character description of the function of that program. This is then used to display on the menus where the respective program number has been used. STYLEman provides you with the facility to translate the standard description to the required language. Enter the details of the required language, in the form of a code and the full program file - only those programs that can be accessed from a menu - is displayed with the entry field displayed. Scrolling through the list enables you to select the required programs. You can then enter your 25 character translation. This description will appear on any menu where that program appears and the operator has the respective language code associated with their Operator Id . 3:20:21 Menu Title Translation In the same way that STYLEman maintains the title for each program so it does the same for each menu within the system. STYLEman also provides the facility to enable you to translate this menu title to your required language. The routine is designed to be as simple as with Program title translation in that you access the current available menus and titles and against each is provided the facility to enter your translation. When an operator signs on to the system with the respective language code associated with their Operator Id they will see the translated menu title displayed. (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE 3:20:22 Message Translation To enable the users of STYLEman to personalise the display and report texts etc. the system has been designed such that all such text is "soft" ie it is not hard coded into the respective programs. The message file holds: Display Text Report Text Warning and Error Messages The translation facility enables you to translate and personalise in the respective language all the field text, header text and titles associated with the respective displays and reports. As warning and error messages are also maintained you also have the facility to translate these as well. Care must be taken at this level though to ensure that the true meaning is not lost or changed in the translation as this may prove confusing to the users of the system. When an operator signs on to the system with the respective language code associated with their Operator Id they will see the translated text when they enter a particular screen or run a report or if the system displays a warning or error message. 3:20:23 Help Text Translation Throughout STYLEman there is both context specific help text and indexed help, providing information about individual fields within a particular display or more wider help regarding the display as a whole. As it may also be necessary for this to be translated into a foreign language STYLEman provides you with the facility to translate the current English text into your respective language. When an operator signs on to the system with the respective language code associated with their Operator Id and they select F2 to access the Help facilities they will see the translated help text. 3:20:24 System Control File Parameter Translation Within the System Control File of STYLEman the codes that you will enter are grouped into Element Types. Each of these Element Types has specific requirements for the entries that are to be made, ie length of code, format of code, variable requirements, etc. To aid the operator the System Control File Parameter File maintains the text that informs the user of the type of entry required. (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE STYLEman provides the facility to translate the contents of this file so that operators signing on in a different language are not disadvantaged by having text in a foreign language. The entries to the System Control File are very important and crucial to the future operation of STYLEman. 3:30 REBUILDS/BATCH OPERATIONS 3:30:10 Introduction STYLEman has been specifically designed to ensure that the operator achieves the fastest possible response to any interactive transaction being undertaken. With this in mind, wherever it was found that the response time was likely to suffer because of the collation of data the building of that data is undertaken in batch. The rebuild and batch operations are mainly restricted to the building of analysis files (eg Customer Analysis, Style and Agent Analysis), availabilities or bulk changes to major files (eg order revaluation). This enables the summarising of many files to be undertaken and the data updated accordingly without disturbing the users on the system. The routines are maintained separately within the system and the System Administrator should determine the frequency with which they should be run and delegate an operator to complete the task. 3:40 ARCHIVE ROUTINES 3:40:10 Introduction To enable you to gain the best information from STYLEman the system has been designed to hold it's data at a detailed level. The consequence of this is that on some of your high activity files the number of records maintained can increase rapidly to a level whereby it becomes detremental to the performance of the system. To aid this situation STYLEman has provided a series of archive routines which allow you to clear records from the files BUT not to delete them. The records are transferred to an archive database where you have the option to either retain them or to back them up on a suitable medium and then delete them from the system. This allows you to ensure that the response times encountered when undertaking interactive transactions are not unacceptably long. It is also possible, if the archive database is retained on the system, to enquire upon its contents through the normal channels . This means that although data has effectively been removed from the files it is not lost from viewing and can still be enquired upon. (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE 3:50 COMPANY SET UP 3:50:10 Introduction For each company used within STYLEman there are two main files which need to be set up which establish the continuing working of the company as they define the operational parameters to be used. The two files are the System Calendar and the System Control File. At first glance it may appear that these are functional details as opposed to system details, this in fact would not be an incorrect assumption. So why have they been included within the System Administrators Guide? As has been described earlier within this guide STYLEman can be broken down into functional areas (eg. Purchase Ordering, Sales Ordering, Costing, etc.) to which are attributed certain programs and set up routines which influence the workings of that functional area. The System Calendar and System Control File influence all functions within the system and therefore it is not possible to assign the responsibility for its upkeep to any one individual. OSL therefore suggest that the System Administrator be responsible for the upkeep of these operations but that he will delegate the preparation and maintenance of the relevant data to respective departments or individuals. It, therefore, becomes the responsibility of the System Administrator to be aware of what is required for each of the elements and to determine who should collate the data and how maintenance should be undertaken. Maintenance of the System Calendar and System Control File need to be carefully monitored. STYLEman is a fully integrated system and a change made by one individual on a control file element may seriously effect the work undertaken by somebody else. It is essential that before an element is actually altered the approval is received from the key users of that element to ensure that they will not be affected. OSL would suggest that this is done by devising a form (see Appendix A, you may take copies of this) which states who has requested the change and the reason for the change. This should then be passed around a pre-defined circulation list for approval or comment. Only when this has been completed should the element actually be changed. It is also worthwhile setting up a notification procedure for all new codes established within an element. This can be done by circulating the input forms which have been filled in (examples for use are supplied in the Implementation Guide) by the requesting operator. Duplication of requests can, therefore, be significantly reduced and thus save the System Administrator a significant amount of time. (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE 3:50:20 System Calendar The System Calendar allows you to define the length of periods that you will be working in for reporting purposes ie Days, Weeks, Months or a User defined Period length. To each period you assign the period number and the days of the year which are to be included within that period. Using the data you have entered STYLEman can allocate data to respective period buckets when summarising details. 3:50:30 System Control File The System Control File establishes the parameters to be used within that particular company within STYLEman and defines the codes and their respective descriptions. The Control File file is made up of a series of elements which allow you to group codes for similar purposes together ( eg. Style colours, cancellation codes, customer payment terms codes, size scales, etc.). Associated with each code is a description which states in 30 characters the purpose of the code ( and may also be used on reports and documentation as descriptive text ) and a series of variable items which are used within the processing of transactions, for example when you establish the code for a salesman/agent one of the variable fields is used to define his standard commission percentage. As the Control File holds the details of codes, associated descriptions and transaction details it is most important that all relevant parties are informed of changes and new additions. 3:60 BACKGROUND DETAILS 3:60:10 Introduction There are a series of function within STYLEman which, under normal circumstances there should be no reason for anybody outside of Option Systems Limited to change. There is one circumstance, though, where a member of the company may wish to actively adjust the details, this being in the case of the Message File. Under normal circumstances any changes to these functions will be carried out by OSL personnel and supplied to you already completed. It is important though that the System Administrator be aware of these facilities in case the situation arises where he may have to use them. (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE 3:60:20 System Control File Parameters As described above the System Control File consists of a number of elements which consist of a code, description and potentially transaction details. The same input format is used regardless of the type of element being entered at that particular time. To aid the operator in the input the System Control File Parameters define for each element the type of entry required and the format it should take. For Example; - should the code be numeric or alpha-numeric, - how long should it be, - what format should it take, - how long can the description be (especially if it is used for external documentation, reports or screen displays), - which variables, if any, are to be used, - are variables left or right justified in there field, - how many places of decimal (for numeric fields) etc. As STYLEman programs expect to receive the data from System Control File elements in a certain format it is essential that these parameters are not altered without the prior approval of a representative of OSL. 3:60:30 Help Text The STYLEman system is supplied with full Help Text available to aid the user in situations where they have forgotten how to undertake a function or cannot remember what type of entry is required. There are two levels of Help available: 1) If the user presses F2 at any time the system will display Help text associated with the field that the cursor was in at that time. This Help text is then specific to that field only and details it's requirements from the operator. This is referred to as Context Specific Help. 2) If the operator requires more general help regarding the screen as a whole, its objectives, the use of the function keys etc., F2 can be selected a second time and a menu of options is made available. The operator can then select the particular category of interest or start with one page and scroll through all the help text available. The actual text itself will be maintained and updated by Option Systems as the system is enhanced and modified. The System Administrator may wish to add to the Help text items which are very specific to the company or the way in which the company operates. This can personalise the help text and make it easier for the operators when they come to use it. (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE 3:60:40 Indexed Help File When an operator selects F2 for the second time, to access Indexed Help the user is supplied with a list of available options from which to select. The index to this wider help option is held and maintained within the Indexed Help File. 3:60:50 Message File The Message File within STYLEman has a two fold function. These are: 1) Within the Message File are maintained all the error and warning messages used by STYLEman programs to indicate problems within the transaction being undertaken. These will be established by OSL and subsequently maintained and updated by OSL as the system is modified and enhanced. There may be the situation where the System Administrator wishes to modify the messages to personalise them to the company's requirements. This can be undertaken, but great care should be exercised to ensure that the meaning is not lost or altered as this may cause confusion. 2) The Message File also contains the literals for the screen displays and the reports within the system. These will be set up by OSL as part of the writing of the respective programs and the file will be updated accordingly when programs are modified or when new programs are written. Because the literals are held in this format STYLEman provides you with the opportunity to personalise the screen displays and reports that your operators use ie. if you call a 'style' an 'item' or a 'product' or a 'part' then you can change the Style Master screen, for example, to require a Part No. or Item No. etc. This allows you to ensure that you can place screens and reports before your operators with terminology that they are used to. This can significantly decrease the time taken to accept the new system by your users. When making these changes care should be exercised to ensure that the available field length for the text is not exceeded and that the meaning of the field is not altered. Just because you have changed the literal of a field it does not alter the way the program processes its contents. (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE 3:70 GENERAL ADMINISTRATION 3:70:10 Introduction Contained within this section on General Administration are some recommendations and procedures related to: - Back up and recovery, - extracting the details of a specific company from a database file to put into a separate database, - exporting data from STYLEman into external packages such as Wordprocessors, Spreadsheets etc - management of printed output ie which printer for which report for which operator etc, It is intended that this be kept as a general section in this format and will be updated as new topics arise. Please notify OSL if there are any further topics that you feel should be discussed. (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE 4:00 PROCEDURES CONTENTS SECURITY Company Details ZZ130-A Company Details Entry ZZ130-M Company Details Maintenance ZZ132-E Company Details Display ZZ137-R Company Details Report Operator Master ZZ120-A Operator File Entry ZZ120-M Operator File Maintenance ZZ120-D Operator File Delete ZZ125-M Password Change and Verify ZZ122-E Operator Master Display ZZ127-R Operator File Report Menu File ZZ140-A Menu File Entry ZZ140-M Menu File Maintenance ZZ140-D Menu File Delete ZZ147-R Menu File Report ZZ517-R Indented Menu Report Program File ZZ210-A Program File Entry ZZ210-M Program File Maintenance ZZ210-D Program File Delete ZZ212-E Program File Display ZZ217-R Program File Report Field File ZZ310-A Field File Entry ZZ310-M Field File Maintenance ZZ310-D Field File Delete ZZ312-E Field File Display ZZ317-R Field File Report (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE SECURITY Security Level ZZ300-A Security Level Entry ZZ300-M Security Level Maintenance ZZ300-D Security Level Delete ZZ302-E Security Level Display ZZ307-R Security Level File Report Security Range ZZ320-A Security Range Entry ZZ320-M Security Range Maintenance ZZ320-D Security Range Delete ZZ322-E Security Range Display ZZ327-R Security Range Report Security Profile ZZ507-R Security Profile Report Security Violation ZZ342-E Security Violation Display ZZ343-D Security Violation Clear System Monitor ZZ332-E System Monitor Display TRANSLATION Program Title Translation ZZ500-A Program Title Translation Entry ZZ500-M Program Title Translation Maintenance ZZ212-E Program File Display ZZ217-R Program File Report Menu Title Translation ZZ510-A Menu Title Translation Entry ZZ510-M Menu Title Translation Maintenance ZZ147-R Menu File Report (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE TRANSLATION Message File Translation ZZ520-A Message Translation Entry ZZ520-M Message Translation Maintenance ZZ152-E Message File Display ZZ157-R Message File Report Help Text Translation ZZ530-A Help Text Translation Entry ZZ530-M Help Text Translation Maintenance ZZ537-R Missing Help Text Report System Control File Parameter Translation ZZ540-A System Control File Parameter Translation Entry ZZ540-M System Control File Parameter Translation Maintenance ZZ102-E System Control File Parameter Display ZZ107-R System Control File Parameter Report REBUILDS/BATCH OPERATIONS RB107-B Order Revaluation Rebuild RB117-B Customer/Order Rebuild RB127-B Style Col/Order Rebuild RB137-B Style Whse/Order Rebuild RB147-B Avail/Order Date Rebuild OP777-B Build Cust/Style Analyses RB157-B Rebuild Avg Days to Pay RB167-B Style Colour/PO Rebuild RB177-B Style/Bulk PO Rebuild RB187-B Avail/PO Date Rebuild ARCHIVE ROUTINES Available in Release 2 (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE SYSTEM SET UP System Calendar ZZ370-A System Calendar Entry ZZ370-M System Calendar Maintenance ZZ370-D System Calendar Delete ZZ377-R System Calendar Report System Control File ZZ110-A System Control File Entry ZZ110-M System Control File Maintenance ZZ110-D System Control File Delete ZZ600-C System Control File Duplication ZZ112-E System Control File Display ZZ117-R System Control File Report BACKGROUND DETAILS System Control File Parameters ZZ100-A System Control File Parameters Entry ZZ100-M System Control File Parameters Maintenance ZZ100-D System Control File Parameters Delete ZZ102-E System Control File Parameters Display ZZ107-R Control File Parameters Report Help Text ZZ220-A Help Text Entry ZZ220-M Help Text Maintenance ZZ220-D Help Text Delete ZZ537-R Missing Help Text Report Indexed Help File ZZ230-A Indexed Help File Entry ZZ230-C Indexed Help File Copy ZZ230-M Indexed Help File Maintenance Message File ZZ150-A Message File Entry ZZ150-M Message File Maintenance ZZ150-D Message File Delete ZZ152-E Message File Display ZZ157-R Message File Report (c) 1991 Option Systems Limited STYLEman SYSTEM ADMINISTRATION GUIDE GENERAL ADMINISTRATION Tailoring of Text Back Up and Recovery Extract Company Details Multi-Company Consolidation Ad-Hoc Reporting Exporting to External Systems Printer Management (c) 1991 Option Systems Limited