PEBC Employee Benefits Enrollment Application and Database Software Maintenance and Support Sample Clauses

PEBC Employee Benefits Enrollment Application and Database Software Maintenance and Support. PEBC Maintenance and Support includes troubleshooting, modifying, upgrading, maintaining, improving security, and enhancing systems and applications which may be running in a production environment. This software is written in C#, housed in Azure, and the data is housed in a SQL Server database. PEBC provides healthcare benefits administrative services for Dallas County, Tarrant County, Denton County, Parker County and the North Texas Tollway Authority. Files are received weekly from each entity related to the health insurance being provided to employees and retirees. These files are reviewed, loaded and processed into the database using the Benefits Administration Software. • The software uses rules engines and stored procedures to: o identify errors in the data; o make corrections; o prepare the information for submittal to insurance providers; and o process files containing information on tax saver and/or health savings plans that are submitted to vendors. • In addition to traditional software maintenance activities of bug fixes, patches, etc., the vendor will also: o provide software development services as needed for development of new features o perform modifications required due to regulatory changes or plan changes of customer entities o Maintain the Azure environment from the standpoint of provisioning users, removing users, ensuring updates to the environment are made using a process that ensure the system continues to operate accurately and performance meet PEBC needs. • Security of the system is critical. This requires: o The vendor to possess and exercise expertise in Microsoft Azure security best practices around, but not limited to: ▪ Network segmentation, ▪ Network Security Groups, ▪ Azure Security Center, ▪ Data security/encryption ▪ Identity management, ▪ Virtual machine hardening, and ▪ Endpoint access control. • All application development must, at a minimum, adhere to the standards outlined in the Open Web Application Security Project’s (OWASP) Application Security Verification Standard (ASVS) at Level 2. • All code changes must be scanned for vulnerabilities before being put to User Acceptance Testing to ensure any weaknesses are addressed. Additionally, all software in use must remain current to provide a secure environment so the vendor will be responsible for ensuring that occurs. Additional responsibilities include documenting and managing the process for adding new users to the system and removing users when requested by PEBC. Th...
AutoNDA by SimpleDocs

Related to PEBC Employee Benefits Enrollment Application and Database Software Maintenance and Support

  • Software Maintenance Subrecipient shall apply security patches and upgrades in a timely manner and keep virus software up-to-date on all systems on which State data may be stored or accessed.

  • Maintenance and Support Services As long as you are not using the Help Desk as a substitute for our training services on the Tyler Software, and you timely pay your maintenance and support fees, we will, consistent with our then-current Support Call Process:

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

  • Routing for Operator Services and Directory Assistance Traffic For a Verizon Telecommunications Service dial tone line purchased by MLTC for resale pursuant to the Resale Attachment, upon request by MLTC, Verizon will establish an arrangement that will permit MLTC to route the MLTC Customer’s calls for operator and directory assistance services to a provider of operator and directory assistance services selected by MLTC. Verizon will provide this routing arrangement in accordance with, but only to the extent required by, Applicable Law. Verizon will provide this routing arrangement pursuant to an appropriate written request submitted by MLTC and a mutually agreed-upon schedule. This routing arrangement will be implemented at MLTC's expense, with charges determined on an individual case basis. In addition to charges for initially establishing the routing arrangement, MLTC will be responsible for ongoing monthly and/or usage charges for the routing arrangement. MLTC shall arrange, at its own expense, the trunking and other facilities required to transport traffic to MLTC’s selected provider of operator and directory assistance services.

  • Software Support Services 6.1 The Software Support Services shall comprise:

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!