(4) Mississippi Code Annotated, Section 31-3-21 requires that any contractor submitting a bid for a public project that (a) involves erection, building, construction, reconstruction, repair, maintenance or related work and (b) will cost in excess of $50,000, possess a Certificate of Responsibility issued by the Mississippi Board of Contractors. This section of the code also requires that all bids submitted for such projects contain, on the exterior of the bid envelope, contractor's current certificate number. Projects involving inside or outside cabling fall within this category and are under the purview of ITS. The total project lifecycle cost is used to determine whether the project requires a certificate of responsibility, which in turn determines who can bid on the project and whether the bid must have the certificate number on the exterior of the bid envelope to be accepted. Guidelines for defining a project:
A project has a specific objective or desired accomplishment and defined starting and ending dates (even if these are rather flexible!). A project is not "business as usual," but a process that is outside the normal flow of work. Projects have a defined scope and a predefined budget and are often executed by contractors or by staff members who are acting outside their everyday work roles.
ITS gives our customers some flexibility in defining a "project," based on the customer's procurement process and guidelines from their auditors. ITS does not make a final ruling but has developed the guidelines below for determining whether expenditures should be considered a single project. The primary "rule of thumb" is that the purchaser document and consistently apply a valid and defensible methodology for defining a project and that the purchaser look at each project separately in regards to vendor selection. ITS suggests the following factors that may determine the definition of an information technology project:
1. A project might be defined by the time frame of the purchases (e.g. all agency workstation procurements for a fiscal year might be a single project; a technology training class would typically be a single project). Note: The 2-way radio EPL specifically defines a "project" for the purpose of the EPL purchase limit as the total expenditures for equipment and services made by an agency from this EPL per fiscal year. 2. Funding source might define a project (e.g. if the funding sources place different requirements on the purchasing entity, separate projects might be needed to accommodate these requirements). 3. In some cases, location of equipment might determine a project (e.g. if each district office can consider a different vendor and/or a different technical solution, these acquisitions could be considered separate projects.) 4. Technical requirements can define a project (e.g. acquisition of several variations of desktop workstations for an agency might be a single project, while the acquisition of desktop workstations for the central office and of ruggedized laptops for the same agency's mobile units might be separate projects). 5. Potential for volume discount can define a project (i.e. Will aggregating requirements for hardware, software, or services across time, locations, or funding sources potentially result in significant cost savings to the state? Will using a competitive process potentially result in better pricing? Note that the instructions for EPLs specify that published prices are not-to-exceed amounts based on a quantity of one. Customers are encouraged to aggregate purchases in order to negotiate for volume discounts from EPL vendors where applicable.) 6. Business functionality and proposed utilization of hardware, software, and services can define a project. (e.g. multiple scanners purchased for general use across an agency might be a standalone project; a scanner purchase for a specific application system for which other hardware, software, and services are also being procured should probably be considered a part of the larger project.)