VMS Requirements Clause Samples
VMS Requirements. 1. Contractor shall provide an operational VMS that is configured to meet the needs of the Lead State and each Participating Entity and Purchasing Entity. The VMS will be operational until the expiration of the Term or the satisfactory completion of the Performance in accordance with a duly issued SOW, whichever occurs later, and must follow the National Institute of Standards and Technology (“NIST”) 800-series guidelines. Contractor shall maintain Security Operation Center (“SOC”) compliance in reportability, availability, confidentiality, and privacy throughout the Term.
2. Contractor shall provide Purchasing Entity with use and access of the VMS within two (2) weeks of a Participating Addendum’s effective date or a Purchasing Entity’s request.
3. The VMS shall provide the processes, components attributes, and functionality described below:
i. Option for on-Site account management and training of staff as required by Purchasing Entity.
ii. Support both the staff augmentation (hourly-based) program and SOW (Deliverable-based) projects.
iii. Electronic SOW completion, approval, and transmission to Contractor.
iv. SOW distribution to Staffing Resource Providers for Contingent Worker availability and cost savings.
v. Contingent Worker staffing search, recruitment capabilities, resume submission, review, verification, and selection capabilities.
vi. Contingent Worker ranking methodologies and capabilities.
vii. Timekeeping, invoicing, validation, and oversight of submitted time.
viii. Reporting capabilities for both standard and ad hoc reports, as requested by the Purchasing Entity.
ix. On-line search and query functions.
x. Tracking, monitoring, and management of Contingent Worker staffing and Contractor Performance.
xi. Capture and manage spend under the Master Agreement and PA.
xii. Other capabilities related to Contractor’s available Services as the Purchasing Entity may request, within the scope of the Master Agreement.
xiii. Configuration, scalability, and flexibility to meet Purchasing Entity needs.
xiv. Maintain active links to contractual position titles and pricing.
4. The VMS must have the capability to receive staffing and project requirements from the Purchasing Entity and provide those requirements to the Staffing Resource Provider; review, rate, and filter the candidates or proposals from the Staffing Resource Provider; send the highest rated candidates and proposals to the Purchasing Entity; capture timesheet information; and accurately invoic...
VMS Requirements a. The Contractor shall provide a plan to implement the VMS within two (2) weeks of the contract Effective Date with projected milestones including the go-live date agreed upon by the State and Contractor. The Contractor shall report progress on the implementation and identify and resolve issues during the implementation. The VMS shall be accessible by End Users through the Internet and reside on a secure server with backup and recovery capabilities as specified in E.17.b, Business Continuity Requirements. The VMS vendor is not authorized to host any Federal Tax Information, Centers for Medicare and Medicaid Services Information or Criminal Justice Information Services Information. The Contractor shall host the VMS and associated data; the VMS and associated data cannot be hosted outside the continental United States.
b. The VMS shall accept requirements from the End User for both Staff Augmentation and Statement of Work requests; provide those requirements to the Sub-vendors; review, rate, and filter the candidates or proposals from the Sub-vendors; send the highest rated candidates and proposals to the End User; capture timesheet information; and accurately invoice the End User.
c. The Contractor shall supply a VMS that includes the following processes, components, and attributes:
i. Sub-vendor Recruitment and Sub-vendor Performance;
ii. Work request (request for services both Staff Augmentation Program and Projects- Based/Deliverables Staffing) distribution in compliance with A.3.a.i.;
iii. Candidate submission and approval;
iv. Scalability and flexibility to unique End User needs;
v. Sub-vendor on-boarding (process by which the Contractor brings Sub-vendors into the VMS system);
vi. Timekeeping (time input, approval/rejection, and alterations);
vii. Reporting (in accordance with Contract Section A.6.); and,
viii. On-line search and query functions.
d. The Contractor shall provide VMS training for all End Users, Sub-Vendors, and Contingent Workers at no additional cost to the State.
e. The Contractor shall provide ongoing support and maintenance for the VMS.
f. The VMS shall store all VMS data for a minimum of five (5) years after date of final payment.