Attachment+A+-+Requirements+Matrix_Engraver.xlsx
XLSX spreadsheet 42 KB Posted
- Attached to
- Engraving Machine
- Solicitation number
- 325-25-990-016
- Issued by
- Wells County, North Dakota
About this file
This is a requirements matrix document for an engraving machine procurement, likely for North Dakota's Life Skills & Transition Center. The document outlines detailed specifications for an industrial engraver with minimum requirements including a 15" x 23" engraving area, capability to engrave items up to 1.875" thick, and compatibility with various materials including metal, glass, acrylic, and wood. The system must include specific accessories such as spindle collets, diamond drag adapters, and vacuum chip removal capabilities. The contract requires a 24-month warranty for parts and labor, with a five-year service contract following the warranty period, and spare parts availability for at least five years from purchase.
The technical requirements specify that the engraver must have USB, Ethernet, and Wi-Fi connectivity, Windows compatibility, and support multiple file formats including JPEG, BMP, TIFF, AutoCAD DXF, SVG, and Adobe Illustrator files. The system must include data retention and purging capabilities, report generation features, and training requirements for two users. The document includes an extensive Enterprise Architecture section requiring detailed responses about system architecture, security measures, data handling, and artificial intelligence usage. No specific pricing terms or funding sources are mentioned in the document.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| IFB+325-25-990-016_Engraver.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Definitions
| ATTACHMENT A - REQUIREMENTS MATRIX |
| Instructions / Directions |
| Offerors must provide a full response to each item number without cross referencing other sections of the proposal. Offerors must use the table format and maintain numbering provided by the STATE to respond to each item number. Attachments, documents, or samples must be clearly referenced where in the response they can be found in the applicable item number. |
A product must be delivered with all Core and a significant portion of Essential requirements represented, and with a plan to implement the remaining Essential requirements in the subsequent phase. A product must be delivered with all Core and a significant portion of Essential specifications represented, and with a plan to implement the remaining Essential specifications in the subsequent phase. Proposals delivering less than Core or Essential will not be rejected. All proposals will be evaluated according to what can be delivered based on the requirements of the STATE.
| Definition of 'Type' | |
| Term | Definition |
| Functional | Impacts the Business Process Requirements that define those features of the product that will specifically satisfy a Consumer need, or with which the Consumer will directly interact. |
| Technical | Impacts the Product Infrastructure Requirements that identify the technical constraints or define conditions under which the product must perform. |
| Operational | Impacts Operations and Support Requirements that define those "behind the scenes" functions that are needed to keep the product operational over time. |
| Transitional | Impacts Implementation Requirements that define those aspects of the product that must be addressed in order for the product to be successfully implemented and to relegate support responsibilities to the Performing Organization. |
| Strategic | Identification of a path to enhance the usability and functionality of the product. |
| Definition of 'Priority' | |
| Term | Definition |
| Core | Requirements that must be included in the solution; otherwise, it will be of no use to the solution. |
| Essential | Requirements for which a short-term work-around may be developed (or for which an old process can be used for a little while longer), but over the long run, the requirements must be implemented. |
| Definition of 'Rating' | |
| Rating | Definition |
| A | Functionality found within the base product and requires no customization or configuration. |
| B | Functionality is in the base product, but requires configuration with no additional costs. |
| C | Functionality requires customization. Provide an explanation as to the complexity of the customization and a cost estimate. |
| D | Functionality is not in the system. |
Requirements Matrix Attachment A
Requirements
| No. | Category | Requirements | Priority | Offeror / Bidder Rating | Offeror / Bidder Response |
| Functional Specifications | |||||
| Technical | |||||
| 1 | Engraving Area | The engraver shall have a minimum engraving area of 15" x 23". The engraver shall fit in a medium-size engraving area. | Core | ||
| 2 | Engraving Depth | The engraver, at a minimum, shall be able to engrave items up to 1.875” thick (3.5” thick or more w/ custom risers) | Core | ||
| 3 | Engraving materials | The engraver shall be capable of engraving on various materials such as metal, glass, acrylic, and wood (that are commonly used in trophies and awards). | Core | ||
| 4 | Accessories | The engraver shall provide spindle collet(s) (if not included) for rotary spindles. The STATEs current spindles are 11/64X6.5) used for engraving (plastic). | Core | ||
| 5 | Accessories | The engraver shall have a diamond drag adapter for etching metals and a vacuum chip removal nose. (if not included) | Core | ||
| 6 | Cooling System | The engraver shall have a built-in cooling system to prevent overheating. | Core | ||
| 7 | Energy Efficiency | The engraver shall be an energy-efficient model to minimize power consumption. | Core | ||
| 8 | Connectivity | The engraver shall incorporate USB, Ethernet, and Wi-Fi connectivity for data transfer. | Core | ||
| 9 | Operating System Compatibility | The engraver shall be compatible with Microsoft Windows. | Core | ||
| 10 | Data Retention | The engraver shall have the ability to purge system of customer data as per client-established data retention policies. | Core | ||
| 11 | Software and file formats | The engraver shall utilize user-friendly engraving software that supports file formats such as JPEG, BMP, TIFF, AutoCAD DXF, SVG, and Adobe Illustrator file (AI). Describe what formats your software supports. | Core | ||
| User Interface | |||||
| 12 | Display | The engraver shall have a functional Touchscreen Display for easy operation. | Core | ||
| 13 | Language Support | The engraver shall include English support, with multilingual support (including Spanish, preferred). | Core | ||
| 14 | Control Panel | The engraver shall have an intuitive control panel with emergency stop button. | Core | ||
| Safety Features | |||||
| 15 | Sensors | The engraver shall have built-in sensors to detect any obstructions or issues during operation. | Core | ||
| 16 | Quick Lock Vise | The engraver shall incorporate a quick lock vise for holding materials in place while being engraved. | Core | ||
| 17 | Emergency Stop | The engraver shall have an emergency stop button that is easily accessible. | Core | ||
| 18 | ADA | The engraver shall have the ability to produce ADA-compliant output, including Braille signage. | Core | ||
| 19 | Customization | The engraver shall have the ability to customize the machine for specific needs, if required. | Core | ||
| 20 | Future Upgrades | The engraver shall have options for future upgrades to enhance capabilities. | Core | ||
| 21 | Reporting | The system shall be able to produce reports based on job data. | Core | ||
| 22 | Report Access | The system shall be able to produce job data in an Excel or csv format. | Core | ||
| 23 | Ad Hoc Reporting | The system shall provide all reports in an ad hoc/on demand manner. | Core | ||
| 24 | Report Examples | The system shall provide, at a minimum, the following reports at go live. | Core | ||
| 25 | Job Proof | The system shall provide a proof document that can be printed and signed by the Life Skills & Transition Center. | Core | ||
| 26 | Job data | The system shall provide a job data report in an Excel or csv format. | Core | ||
| 27 | Export Formats | Reports shall in the form of a pdf and Excel. | Core | ||
| Transitional Specs | |||||
| 28 | Training | Currently the print shop has 2 users. The CONTRACTOR shall provide training on the engraver. | Core | ||
| 29 | Minimum Training Requirements | The CONTRACTOR shall provide, at a minimum, the following: |
- eLearning (required)
- Training Manuals--electronic (required)
- Training development for installation, operation and maintenance.
- Desktop procedure documentation with a comprehensive user manual, troubleshooting guide, and maintenance instructions.
- Training documentation repository.
| Core | |||
| 30 | Literature | The Bid Response must include descriptive literature or detailed manufacturer specifications for the offered equipment or commodities. Bidders are instructed to clearly mark the literature that demonstrates compliance with the specifications. Indicate whether optional features are included to meet the specifications | Core |
| Operational Specs | |||
| 31 | Record Retention | The engraver software system shall have the ability to permanently purge data/records in a systematic way according to policy and after the legally prescribed retention period. | Core |
| 32 | Retention Schedule | The engraver software system shall be able to create a retention schedule for the Life Skills & Transition Center records. | Core |
| 33 | Retention Schedule Review | The engraver system shall give users the ability to review the retention schedule. | Core |
| System Maintenance Plan/Support / Service Contract |
The BIDDER shall, at a minimum, provide:
| 34 | Service Contract | a. a Service Contract for five (5) years (60-month term). | ||
| The service contract shall begin immediately after the warranty period ends. The Bidder must attach their detailed maintenance and support plan/Contract. To comply with North Dakota State laws and rules, the State reserves all rights to amend and negotiate the service contract and related documents. | Core | |||
| 35 | Maintenance | b. a detailed maintenance plan including scheduled servicing and parts replacement. The BIDDER shall supply ongoing technical support and service availability. | Core | |
| 36 | Warranty | c. The CONTRACTOR shall have a minimum of 24 month warranty for parts and labor, with an option for extended warranty. | Core | |
| 37 | Parts | d. The CONTRACTOR shall make spare parts available for at least 5 years from the date of purchase | Core |
Ent Arch Specifications
| # | ENTERPRISE / ARCHITECT SPECIFICATIONS |
| Architecture - IT Application Questions |
Proposals MUST include a response to all the IT Application Questions: E1 - E15. The following section contains technical questions for this solution. The offeror MUST provide answers to each question in the attachment.
| No. | Enterprise IT Standards |
| E1 | Offeror must describe in detail the architecture of the proposed solution and supporting infrastructure. |
| a. Include the technology stack, including the software products and programming language used to create the solution | |
| b. Include the network and infrastructure architecture, including security levels, connectivity points, and capacity | |
| c. Include the storage architecture, including security controls (i.e. encryption) | |
| d. Include related architectural diagrams | |
| Offeror Response: | |
| a. | |
| b. | |
| c. | |
| d. | |
| E2 | Offeror must describe the solution’s integration points with other applications or datasets, and other external dependencies. |
| Offeror Response: | |
| E3 | Offeror must describe the solution’s ability to provide high availability. |
| Offeror Response: | |
| E4 | Offeror must describe the solution’s ability to be enhanced to implement changing business and technical requirements. |
| Offeror Response: | |
| E5 | Offeror must describe the solution’s ability or limitations for migrating solution elsewhere in the future with regard to either party terminating services. |
| Offeror Response: | |
| Data | |
| E6 | Any DATA provided by the STATE must be accessible to the STATE at any time. |
Offeror must describe how the proposed solution ensures the STATE can access all provided data anytime (API, SQL, batch export, etc.) and detail data export options (formats, ETL, encryption, required software) for portability evaluation by the STATE.
| Offeror Response: | |
| E7 | Offeror must describe the controls used to insure data is properly classified and how sensitive/confidential data is safeguarded. |
| Offeror Response: | |
| E8 | Offeror must describe the practices and procedures used to provide Electronic Discovery of specific records or data, and any legal positions regarding subpoenas, jurisdiction and potential confiscation of data. |
| Offeror Response: | |
| Artificial Intelligence | |
| E9 | Offeror must indicate if the proposed solution uses GenAI technology, model, or service. |
| Offeror Response: | |
| Security | |
| E10 | Offeror must describe if the proposed solution FedRAMP, HITRUST, or StateRAMP authorized. |
If no, are there plans to seek authorization?
SaaS solutions containing Federal Tax Information, Social Security Administration, or Criminal Justice Information must be FedRAMP authorized.
| Offeror Response: | |
| E11 | Offeror must describe the controls used to measure and meet regulatory requirements and certifications. Include any Application Scanning reports, Vulnerability Scanning reports, and Penetration Testing reports. Include schedules for recurring/updated reports. |
| Offeror Response: | |
| E12 | Offeror must describe the controls used to manage operational logs for troubleshooting and regulatory compliance. |
| Offeror Response: | |
| E13 | Offeror must describe the controls used to ensure that privileged users cannot perform unauthorized or unlawful activities. |
| Offeror Response: | |
| E14 | Offeror must describe in detail the ability to configure and implement a session timeout due to inactivity. |
| Offeror Response: | |
| E15 | Offeror must describe in detail the proposed solution's privacy and consent controls. |
| Offeror Response: |
File details come from the government source that posted it. Updated .