Laserfiche WebLink
Business Analyst I..BI, process flows, design studio <br />(.5 -1.0 FTE per suite) <br />1.5 -3.0 <br />System A_lministrator,Database Adni nlstr;uo: 'A,ch <br />Urninistr,;tor SeCUrity U n nisiralor <br />1'5 _2.0 <br />Lawson Manauer <br />0.5 -1.0 <br />Subject 'Matter Experts (SNIE) <br />varies <br />4. What types of skill sets are necessary for technical and functional support staff? <br />Lawson Response: <br />The skill sets necessary lrar technical and functional support staff are the same prerequisite skills for the project team <br />members. Those skills are noted in the response to Section I1L (4) below. <br />S &S Response: <br />The skill sets necessary for technical and functional support staff, as stated by La4vson abo%e, are the same skills for the <br />prqject team members. The two largest facets of ongoing support are End User Support and System Administration. <br />From an end user perspective, the City is responsible f>r providing the functional expertise of both the enQuesta <br />application and business processes to support first level end user issues. From a System Administration perspective, the <br />City is responsible for ongoing maintenance of enQuesta as it relates to security, database administration, management <br />of the network and hardware, including printers and other peripheral devices, management of interfaces and third <br />parties, and testing of maintenance releases before deployment to the City's production environment. <br />5. Our business units may need to research detailed tasks after they have been archived from the live system. <br />Over time the old data may reside on a database /application that is quite different from the current live one. <br />How are these issues handled? <br />Lawson Response: I -awson applications have a complete purging - archiving capability, see responses below under <br />Archiving and purging. This detail will be discussed further in the Technical Session. <br />S &S Response: enQuestaT_'" leverages database partitioning for real time archiving of historical data. This means that <br />the data will continue to reside within the production database instance. Partitioning allows for a single datastore, <br />accessible by all normal means, while simultaneously maintaining the performance as if there were only a limited <br />number of "years " of data on the system. <br />6. Each business unit (i.e., payroll vs. AP vs. GL) may have different criteria for purging/archiving data. How is <br />that handled? <br />Lawson Response: Lawson applications have a complete purging - archiving capability, see responses below under <br />Archiving and purging. This detail will be discussed further in the 'Technical Session. <br />7. In the Functional Requirement you indicate that the system will handle: <br />■ Archiving and purging of data (tech 4.06, tech 4.07). <br />Lawson Response: Lawson delivers for eNery major module programs used to identify information for the <br />purpose of archiving and extraction from the OLTP production database. These programs create the necessary <br />file extracts needed to preserve the information in a format that can easily be transferred to archive products, <br />archive databases or industry standard backup methods such as tape drives. <br />■ Provide method to access archived data when system architecture changes as a result of software upgrade (tech <br />13.00) <br />Lawson Response: Lawson generally provides the ability to extract and archive information for use with <br />other archiving products. The ability to access these archive files are generally dictated by the method of <br />archive and the standard access methods available to these products. You should always have 'Lill access to <br />archived data and in some cases the information is stored into an archive data mart. <br />■ Archives /purge records upon request within a user - defined time and criteria (tech 14.00) <br />Lawson Software — Confidential 4 <br />