Technical Specifications

Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score Following are the Vendor Availability Rating definitions: Available (A) existing capability. System will accomplish requirement using Development (D) System will accomplish requirement with package modification and will be included in future releases of the package without custom modification to the NCCCS package by end of Phase I estimated to be by 12/31/2001. Customization (C) System will accomplish requirement with modification and will NOT be included in future releases of the package. Each future release will require custom modification to the NCCCS package by end of Phase I estimated to be 12/31/2001. Not Available (N) System cannot accomplish requirement. Offerer should provide written risk analysis and justification for accepting a proposed system that cannot accomplish the specific requirement, such as the reason that a requirement is not applicable to the proposed system. 4.1.0 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 System Design and Architectural Environment The proposed product suite must operate in the current technical environment of the NCCCS. See the description of that environment in the earlier section of technical requirements. Must define all vendor specific terms used in your responses to the RFP. Must provide a component interaction diagram of the product suite offered in this response to the RFP (a sample of the diagrams must be provided in the response). Fully describe and illustrate the architecture of the product suite including all options, what executes where, e.g., client/server, host based, and what is stored where. The proposed product suite must be modular in design, e.g. security operation and system support must be enabled within each module (Student Information, Human Resources, etc). Server Platforms Identify each of the supported server platforms (e.g., platform where the database resides, platform where batch processing will be performed) for the product suite including the hardware platform operating system and operating system versions. The product suite must be supported on POSIX compliant operating systems. The supported systems should include the Sun Sparc Solaris, IBM RS 6000 AIX, and IBM OS 390, the current installed base of the NCCCS. A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A 4.2.0 4.2.1 A Please refer to the Technical Specifications Descriptions for additional information. 4.2.2 A Please refer to the Technical Specifications Descriptions for additional information. Page 1 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.2.3 4.2.4 4.2.5 4.2.6 4.2.7 4.3.0 4.3.1 4.3.2 4.3.3 4.3.4 Proposed suite versions must be maintained to a within a one year lag compatibility with the latest major release (x.x0 release level) of the underlying DBMS and platform operating systems. Early release of the product suite in the environment of the NCCCS is critical. For a new release of your proposed product suite, list the priority of releases on server operating systems upon which your systems operates. Define the hardware needed to provide ongoing support for college installations as a function of per fifty concurrent users, e.g., <50 users, >50 but <100, >100 but <150,...>200 but <250, etc. Define the FTE personnel support needed to provide ongoing support for college installations as a function of per fifty concurrent users, e.g., <50 users, >50 but <100, >100 but <150,...>200 but <250, etc. The application suite must be supported on older versions of the operating systems. Describe your policy and timing for dropping support of older versions of each server operating system and for dropping support of operating systems that are not in high usage in your customer base. Client Platforms All client side components of the product suite must be supported on Microsoft Windows 95, Windows NT, and Windows 98 clients. Identify each of the supported non-web client platforms for the product suite including the hardware platform operating system and operating system version. Some features must be available via the web. Identify each of the supported web client platforms for the product suite including the hardware platform operating system and operating system version. Describe how Macintosh clients are supported. Proposed suite versions must be maintained to a within a one year lag compatibility with the latest major release of the supported client platforms operating systems. Describe your policy and timing for dropping support of older versions of each client operating system and for dropping support of operating systems that are not in high usage in the customer base. Higher cost platform configuration requirements will not be rated highly. Define the minimum hardware configuration for each client platform for both Internet users and non-Internet users. Higher cost platform configuration requirements will not be rated highly. Define the optimal hardware configuration for each client platform for both Internet users and non-Internet users. Database Management Systems (DBMS) All questions in this section must be responded to for each DBMS included in the cost model. Support of more than one DBMS is desirable. Identify each of the supported DBMSs and versions for the product suite. A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A Please refer to the Technical Specifications Descriptions for additional information. A A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.3.5 A 4.3.8 A 4.3.9 A 4.4.0 A A Page 2 of 23 4.4.1 Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.4.2 4.4.3 4.4.4 4.4.5 4.4.6 4.4.7 4.5.0 4.5.1 Maintaining synchronization of applications to DBMS version is desirable. For new versions of each DBMS that you support, provide the elapsed time from the release of the database by the vendor until you provide your customers with a certified version of your software for that database version. Involving users in determining when to drop support of older versions of a DBMS is desirable. Describe your policy and timing for dropping support of older versions of each database. A common data dictionary must be provided that defines each database table and field. For each object defined in the dictionary describe in detail all attributes available to define the object. Include a sample of one complete dictionary element. The NCCCS must be able to easily modify the DBMS. Describe the recommended approach for customers to add fields and tables to the database. The ability to populate DBMSs across multiple servers is desirable. Describe the options available to distribute data across multiple database servers to balance workload. Describe any data redundancy required to support this capability. Specifically indicate if support for different DBMSs is possible. The ability to populate DBMSs across multiple servers is desirable. Describe the support for transaction management when a logical transaction updates databases on multiple database servers (e.g. two phase commit). Describe any additional software and cost requirements to support this function. User Interfaces A user friendly interface is important. Describe for browser and nonbrowser each of the ways that a user can initiate commands (e.g. using drop-down menus using keystrokes). Indicate if all or only selected commands can be initiated by keystrokes. Describe deviations from Windows standards. Adherence to ADA rules is important. Describe how you support the accessibility requirements defined by the Americans with Disabilities Act. Look at Windows 95 control panel accessibility options. The product suite must provide the capability for inter-module navigation, with proper user access rights, from process to process across the entire suite. Customer ability to provide custom views to its users is important. Describe the capabilities for the customer to customize their navigation build their own menus. The ability to provide customized transaction sequencing is desirable. Describe the capabilities within the product suite to support sequencing transaction entry forms by the customer to support business work flow. Please refer to the Technical Specifications Descriptions for additional information. A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A Please refer to the Technical Specifications Descriptions for additional information. A Please refer to the Technical Specifications Descriptions for additional information. A 4.5.2 A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.5.3 A 4.5.4 A 4.5.5 A Page 3 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.5.6 4.5.7 4.5.8 4.6.0 4.6.1 4.6.2 4.6.3 4.6.4 4.6.5 4.7.0 4.7.1 4.7.2 4.7.3 4.7.4 4.8.0 Single user logins are required to access multiple functional portions of the application (e.g. human resources payroll financials student) by the same user. User access to services via telephone is important. Describe all transactions (e.g. grade inquiry registration payment of fees schedule inquiry financial aid inquiry etc. etc. etc.) where touch-tone capabilities have been incorporated into the product suite. Describe the hardware and software platforms required to deliver the touch-tone features of the product suite. Some colleges may need to use character-based terminals to perform some functions. Describe the support for character based terminals within the applications including what services are available via terminals. Network Support Adherence to data communications standards is important. Describe any software required to support communication between application components running on different platforms. Any costs associated with this software must be included in the cost model. The TCP/IP communication protocol must be supported. New development modules must adhere to the NC Technical Architecture for Networking (see URL referenced in 24) The product suite must co-exist in an environment that includes servers running Novell 4.x and up. The ability to perform functions in a distributed environment is desirable. Describe your support of the Distributed Computing Environment (DCE) or similar technologies. The ability to FTP files from the colleges to the systems office and others is required. Describe how the product suite enables this function. Tools and Languages Application development environments that enable fast development and easily managed application maintenance are important. Describe all tools and languages used to create the product suite. Also describe how each tool or language is used. Identify the Specify any third party products required to run the software or to use specific features of the software. Describe the role of the third party products. Include costs in the cost model. Specify other optional third party products that the product suite interfaces with. Show the cost of each product in this response. Source code and documentation must be made available to the customer in the event the provider for any reason discontinues support of the proposed product suite. Verifiable escrow accounts with viable third party escrow service companies with customer triggered release terms will receive highest scores. Describe the policy for providing source code and documentation to customers. Design and Features A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A Please refer to the Technical Specifications Descriptions for additional information. A Please refer to the Technical Specifications Descriptions for additional information. A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A Please refer to the Technical Specifications Descriptions for additional information. A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A Page 4 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.8.1 4.8.2 4.8.3 4.8.4 4.8.5 4.8.6 4.8.7 4.8.8 4.8.9 4.8.10 4.8.11 4.8.12 All components of the product suite must utilize a single, integrated, Database Management System and provide seamless processing at those points where the components share data. All modules must be highly integrated with each other where appropriate thus reducing information redundancy and improving data integrity. Describe the integration (i.e.. real time or batch integration) between the curriculum student, continuing education, student financial aid, financial, HR, payroll systems, and any other proposed modules. User control of the product development decisions is important. Describe what role the NCCCS will have in determining the enhancements and bug fixes to the proposed product suite. If your product is rules-based, then ease of applying rules and the ability to isolate users from rules administration is important. Describe the extent to which the product suite is rules based. Using examples describe how rules are defined. Describe how you insulate the user from the complexity of setting up and maintaining the rules. All suite features should be available on all supported platforms. Describe all features of the product suite that are available on one platform and not supported on another platform if any. Include both clients and servers. The ability to monitor performance and tune systems to improve performance is important. Describe the features you have designed into the product suite to provide the best possible performance. Address network traffic, end user response time, and server processor impact. Indicate if these features apply across all platforms. suite must fully supports the upcoming century change in The product terms of dates, derived time periods (e.g,. academic terms), and other impacted areas. The vendor must certify that the product suite and required third party software are fully year 2000 compliant. Different users will require different views and access needs to the information in the system. Describe how the database design or specially designed application features support operational needs, adhoc reporting needs, college research needs, and executive information needs. Assuring consistency between the product suite and underlying systems infrastructure is important. Describe the features of the product suite that insure that the version of software executing on the client matches the version of software and database on the server. It is required that the proposed product suite enable the customer control of event logging. Describe the design for event logging management. Applications that have fat clients are not as desirable as those with thin clients. Describe the distribution of application processing between the client and server(s) including all options available. A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A Please refer to the Technical Specifications Descriptions for additional information. A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A Page 5 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating A Vendor Reference Evalua- Raw Score tion Score Extended Score 4.8.13 4.8.15 4.8.16 4.8.17 4.8.18 4.8.19 4.8.20 4.8.21 4.8.22 4.8.23 The ability to tract processing statistics is desirable. Describe processing statistics maintained by the product suite. There will exist some occasions when mass changes to a database are required. Describe the features of the product suite that support the ability to make mass changes to the value of data in a field for selected records. Data integrity and reduced redundancy are important. Describe data that are commonly defined and shared across all business functions supported by the product suite (e.g. names, addresses, phone numbers, facilities, departments). Describe how that common definition is supported within the product suite. The ability to annotate data with comments and note is desirable in some cases. Describe the support for the entering of comments and notes attached to records and what entities/tables this feature is available for. Multiple campus colleges must be supported. Describe how the product suite supports multi-campus colleges including the specific cases where data can be common for all campuses or unique for each campus. The NC State Board for Community Colleges maintains databases of information collected from each of the state's community colleges in electronic, automated processes. Describe the capabilities of the product suite that will help facilitate this reporting requirement. The product suite must provide support for time-relational data; past, present, and future as appropriate for each business function. Define your methodology for meeting this requirement. Describe any aspects of the product suite that will limit 24x7 processing for online users (e.g. web enable student access). The product suite must accept, edit, and process bulk data from external sources. Describe all types of data that can be processed in this manner. Identify all features of the application that require background (batch) processing. Provide your definition of background (batch) processing. Most transaction must be posted immediately to the DBMS. Identify any online transactions that are not fully posted immediately when the transaction is entered. Describe all transactions that support notification to one or more persons when the transaction occurs. Customization - tools must be included in cost model Customized reporting is required in all modules. Describe the capabilities included in the product suite to enable the development of customized reporting both for the standard package and for each college. Customization of on line forms is required. Describe the capabilities available for colleges to customize on line forms. A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A Please refer to the Technical Specifications Descriptions for additional information. A Please refer to the Technical Specifications Descriptions for additional information. A Please refer to the Technical Specifications Descriptions for additional information. A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A 4.8.24 A A 4.8.25 4.9.0 4.9.1 A 4.9.2 A Please refer to the Technical Specifications Descriptions for additional information. Page 6 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.9.3 4.9.4 4.9.5 4.9.6 4.9.7 4.9.8 4.9.9 4.9.10 4.10.0 4.10.1 4.10.2 4.10.3 4.10.4 4.10.5 The ability for the customer to customize certain attributes of the product is required. Describe the capabilities available for colleges to customize data validations. The ability for the customer to customize certain attributes of the product is required. Describe the capabilities available for colleges to customize processing rules. The ability for the customer to customize certain attributes of the product is required. Describe the tools and process for customer customization of the product suite to meet unique needs. The ability for the customer to customize certain attributes of the product is required. Describe how customizations of the software impact the software maintenance agreement and support. The ability for the customer to customize certain attributes of the product is required. Describe any features of the product suite that help the customer reapply their customizations to new software releases. The ability for the customer to customize certain attributes of the product is required. Describe API's available for integrating customizations and other software with the product suite. The ability for the customer to customize certain attributes of the product is required. Describe the process that a customer must go through customize or modify the application software to meet changing business requirements. The ability for the customer to customize certain attributes of the product is required. Describe the built in features (no programming required) of the product suite that support adding college unique data that needs to be collected and reported on. Internet User access to certain product functions via the Internet are required. Describe the technology used to delivery the World Wide Web features of the product suite including all required hardware and software. Describe all supported browser platforms and web server platforms including valid combinations of browser browser version operating system version. Authentication and Encryption security processes are required for some processes e.g. student access to web enabled processes. Describe how security defining a user's access to records is implemented for web transactions. Describe any options available to customize the web features of the application. Describe how the capabilities and features differ between the web browser version for an application function and the non-browser version of that function. A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A Please refer to the Technical Specifications Descriptions for additional information. A Please refer to the Technical Specifications Descriptions for additional information. A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Page 7 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.10.6 4.10.7 4.10.8 4.10.9 4.11.0 4.11.1 4.11.2 4.11.3 Proposed suite versions must be maintained to a within a one year lag compatibility with the latest major release of the supported web browser systems. Describe all transactions where World Wide Web access has been incorporated into the product suite for student self service. Describe all transactions where World Wide Web access has been incorporated into the product suite for faculty self service. Describe all transactions where World Wide Web access has been incorporated into the product suite for staff self service. Archival Archiving all historical data is required. Describe the technology used to archive historical data from the application database for purposes of offline record retention and potential reactivation of the records including associated costs. Describe any data that cannot be archived. Describe the options for tracking and cataloging the specific media (e.g. DAT CD ROM DASS ) archived data is stored on and what the time frame of data is. The archived data must be retrievable for use with an option to reload previously archived data back into the database including data archived from previous information systems. Describe the options available to move data to alternative storage (e.g. hierarchical file system) based upon the age of the data. The product suite must support data archiving and purging based on user-defined retention schedules for each type of data. Imaging Imaging technologies are required options for the product suite. Describe the technologies used to support imaging technologies. Describe how imaging is integrated in the product suite. Describe all areas (e.g. financial aid applications) where imaging has been incorporated into the product suite. Work Flow - Electronic Routing and Approvals The proposed product suite must provide a means by which the customer can apply work flow processes to items of choice. Describe the technology used to support electronic routing and process of customer work forms. Include information on costs associated with this feature. Work flow processes must include the capability for electronic signatures where needed. Describe the means by which electronic signatures are enable to customer selected work flow processes. Include any cost associated with this feature. Describe all business transactions where electronic routing and approvals have been incorporated into the product suite. A A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.11.4 A A A 4.11.5 4.11.6 4.12.0 4.12.1 4.12.2 4.12.3 4.13.0 4.13.1 A A A A 4.13.2 A Please refer to the Technical Specifications Descriptions for additional information. 4.13.2 A Please refer to the Technical Specifications Descriptions for additional information. Page 8 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating A A A Vendor Reference Evalua- Raw Score tion Score Extended Score 4.13.3 4.13.4 4.13.5 4.14.0 4.14.1 Describe the options and rules that are available to define how a transaction is route. Describe how routing paths are setup (e.g. using roles positions or specific individuals). Describe the features available that make it easy and efficient to setup the routing rules for different types of transactions. Electronic Mail Interface Describe the technology used to support the transmission of application messages and output via the GroupWise E-mail system. Use of e-mail to communicate process actions e.g. process transmits a file to the system office is required. Describe all areas where electronic mail integration has been incorporated into the product suite and how customized applications of E-mail process into the product suite is accomplished. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A 4.14.2 A Page 9 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.15.0 4.15.1 4.15.2 4.15.3 4.15.4 4.16.0 4.16.1 Electronic Data Interchange (EDI) - include any costs in cost model Use of EDI technologies is required to meet the needs of such functions as electronic transcripts. Describe the technology used to support electronic data interchange (EDI) e.g. extended markup technology. Describe all business transactions where EDI capabilities have been incorporated into the product suite. Support of the SPEEDE Express EDI standard for transmission of electronic transcripts is required. Describe the means by which the proposed product suite support s this standard. Describe application where electronic funds transfer is enabled. Desktop Product Integration Integration with the Microsoft Office desktop office automation tools is required. Describe how the product suite is integrated with desktop tools such as spreadsheets word processors and database packages including the technologies used for integration (e.g. downloading files DDE OLE). Describe all business transactions where desktop product suite (e.g. spreadsheet word processing) integration has been incorporated into the product suite. Security Describe any integration between the product suite's security operating system security and network operating system security. Describe the security reporting available for purposes of audit (e.g. application functions each user can access user access to the database). Describe the security features of the product suite for allowing user access to specific processes and functions (e.g. add change delete). Describe the granularity of the process based security. Describe the security features of the product suite that control individual user and group access to specific records in the database (row level security). Indicate if this security applies to read update or both. Indicate if this security is enforced by the application software the DBMS or the platform operating system. Describe the methodology for the customer to assign row level security (e.g. student records enrollment records course records financial records budget records). Describe the methodology to implement security features of the product suite that control user access to specific fields in the database (column level security). A Please refer to the Technical Specifications Descriptions for additional information. A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A 4.16.2 A Please refer to the Technical Specifications Descriptions for additional information. 4.17.0 4.17.1 4.17.2 A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.17.3 A 4.17.4 A 4.17.5 A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.17.6 A Page 10 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.17.7 4.17.8 4.17.9 4.17.10 4.17.11 4.17.12 4.17.13 4.17.14 4.17.15 4.17.16 4.17.17 4.17.18 4.17.19 4.17.20 4.17.21 Encryption is required for some data elements. Describe the product suite's support for customer defined encryption of data within the database. List each field that can be stored encrypted such as passwords PIN's credit card numbers evaluation ratings. Describe the products or algorithms that are used for encryption. Describe the product suite's support for encryption of data across the network for non-web based transactions. Include information on communications between client and server and server to server. Identify any third party products required and include the costs in the cost model. Users must be able to change their own passwords for any application maintained passwords. Any application maintained user passwords must expire after a specified period of time. Describe how the time period is defined (e.g. by user globally for all users) and if it is customizable. Describe how the product suite limits a user from reusing the same application password within a period of time. Describe the protections built into the product suite for unattended workstations (e.g. time-out capabilities). Describe the options available to control the length and content of user passwords. Describe how the product suite prevents the user from using a "easy to guess" password. A user must be disabled after a specified number of invalid login attempts from within the product suite. Describe how the rules regarding invalid login attempts are specified. Invalid login attempts must be logged for any logins that are managed by the product suite. Providing an audit trail of user access is required. Describe features of the product suite that provide an audit trail of a user's access to and use of the application and application processes. Describe the features available in the product suite that make the setup of application security efficient and easy for the user responsible for security setup (e.g. the use of copy capabilities security templates definition of roles). Describe the features available in the product suite that support the capability to distribute the setup of application security in a college that are responsible for the data. Describe how security for student access is provided at the operating system database and transaction level. Describe the security features available in the product suite that support the concept of a "user class" (e.g. student faculty) where there is one user setup in the application and one shared system login is established. People logging in to one of these "user classes" will have the security applied to the class. Please refer to the Technical Specifications Descriptions for additional information. A Please refer to the Technical Specifications Descriptions for additional information. A A A A A A A A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A Page 11 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.17.22 4.17.23 4.17.24 4.17.25 4.17.26 Support for begin and end dates for a user (i.e. they cannot access the system until the begin date and they cannot access the system after the end date). Provide an interface so that a user can be automatically updated with an end date when separated from employment. Provide the capability to manually deactivate and reactivate a user. Track the date the user last used the product suite. Provide the ability for a college to create and display a message to staff regarding the Family Education Rights and Privacy Act (FERPA) when they log in to the application. Describe any other security features that have not been covered. Names Addresses and Phone Numbers Support the entry of name into multiple fields (e.g. last first middle). Describe all fields available. Support the storage of mixed case names. Describe all formats available for the entry and storage of names (e.g. in one field in separate fields all caps mixed case etc.). Describe the information maintained related to a history of name changes for a person. Describe how the product suite supports storage of names addresses phone numbers and other information that is not business function specific for persons vendors or businesses in single shared repository. Support multiple addresses for a person. Describe any system defined addresses that are available. Indicate if the customer can define their own types of addresses. Describe the product suite's ability to comply with the USPS's requirement for CASS certification of addresses. Describe when and how the CASS certification is accomplished. Contact your post office for information. Describe the product suites' capability to print "POSTNET" formatted bar codes on correspondence such as student quarterly grade mailer. Identify any hardware requirements to support this feature. Describe the plans to keep up with changes in postal regulations and to insure that colleges can receive the best possible rates from the USPS for documents that they mail. Support multiple phone numbers for a person. Describe any system defined phone numbers that are available. Indicate if the customer can define their own types of phone numbers. A A A A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.17.27 4.18.0 4.18.1 4.18.2 4.18.3 4.18.4 4.18.5 A A A A A 4.18.6 A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.18.7 A 4.18.8 A Please refer to the Technical Specifications Descriptions for additional information. 4.18.9 A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.18.10 A Page 12 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.18.11 4.18.12 4.18.13 4.18.14 4.18.15 4.18.16 4.18.17 4.19.0 4.19.1 4.19.2 4.19.3 4.19.4 4.20.0 4.20.1 4.20.2 4.20.3 4.21.0 Describe any API's or processes available to synchronize names and addresses with other third party products that contain names and addresses. Describe all ID's available to identify a person (e.g. SSN user defined ID's). Describe the options available for maintaining the confidentiality of names addresses and phone numbers for individual records in the database. This is to maintain compliance with FERPA requirements when a student or employee requires that their information be Describe the features that prevent users from creating multiple sets of records for the same person, vendor, or business. Support National Change of Address (NCOA) processing to insure that the person is valid for the address. Describe products used to support this feature. Contact your post office for details. Describe features that allow individuals to directly update their personal information. Describe the product suite's capability of using alternate indexes. Indicate how the product enables the establishment of new indexes and the need arises. Future Plans for the Product Suite Provide a position paper describing your plans and strategies to extend Internet and Intranet based solutions. Discuss your planned architecture including tools target users scope of deliverables (e.g. what business functions) and the time frame when you will implement your plans. Describe any planned changes in the platforms that the product suite is using. Indicate the time line for any changes. Describe any planned redevelopment of all or a portion of the product suite in new or different tools or languages. Describe the time line for completing the redevelopment. Describe plans for enhancing the product suite's design and feature set including timing. Online Help and Documentation On-line help and documentation is required. Describe the areas for which context sensitive help is available to the end user (e.g. help on field help on process help on message). The ability for customer enhancement of the on-line help systems is required. Describe the options including tools and methods that are available to customize the on-line help. Describe all other types of on-line documentation available to the end user as they use the application e.g. electronic user manuals training courses, etc.. Operations Management A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A A Page 13 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.21.1 Provide information on tools to support the end user scheduling of batch jobs and the management of batch operations. Indicate if these tools are included in the cost model or are recommended tools. Describe any capabilities within the product suite to support workload balancing across available processors in a multi-processor platform. Describe the tools that are provided to assist the customer troubleshoot application problems and if necessary recover data. Describe the tools that are provided to assist with implementing the software and software updates across multiple platforms. Major releases must not be so frequent as to impede effective administration and must be fully documented itemizing new features, fixes, deleted features, databases changes, view changes, and other changes that impacts customs modifications or application operations. Patch releases must be done in such a way as to make installation and tracking easily accomplished. Describe the methodology for issuing and installing new releases, both major and minor, of product suite modules. End User Tools Provide information on tools for end users (not technical staff) to create ad-hoc reports and create files to be used in client based office applications. Include a description of the tools that provided to enable the allocation and use of system resources. Indicate if these tools are included in the cost model or are recommended tools. For tools included list their cost in the cost model. Row and column security must be enforceable when using third part tools to access databases. Describe how the row and column level security can be enforced when using third party data access tools. Describe any data warehousing/OLAP capabilities associated with the product suite. End users must have the capability of developing decision support systems related to their needs. Describe any decision support or executive information capabilities associated with the product suite. The NCCCS must have the right to copy and distribute documentation to the college users. Documentation must be available in electronic format. Describe the documentation and tools available to provide end users with knowledge of the database tables and fields to assist them in ad-hoc reporting. Development and Implementation Describe the methodology for implementing the product suite in the 59 institutions of the NCCCS and the cost for implementation. A Please refer to the Technical Specifications Descriptions for additional information. 4.21.2 A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.21.3 4.21.4 4.21.5 A 4.22.0 4.22.1 Please refer to the Technical Specifications Descriptions for additional information. A 4.22.2 A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.22.3 4.22.4 4.22.5 A 4.23.0 4.23.1 A Please refer to the Technical Specifications Descriptions for additional information. Page 14 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.23.2 4.23.3 Describe the options for providing training to the product users in the 59 institutions of the NCCCS. List the projected costs for each option. At least two options must be described, 1. Train-the-trainer (training of 22 NCCCS staff at the NCCCS System Office location), and 2. Vendor trains all college users as per the list of colleges referenced in the appendix. The vendor must provide training materials via machine readable media that can be copied by NCCCS and/or colleges for internal use. The vendor must also provide a tape or CD-ROM of necessary training files, databases with installation instructions. These materials will be used for refresher courses and training new employees. Describe the options for providing training to the 17 technical support staff on the administration and operation of the product suite in the 59 institutions and the NCCCS System Office Information Services Section. List the projected costs for each option including as a minimum a train-the-trainer option and a vendor supplied training option. The vendor must allow all training sessions to be video taped by NCCCS staff or college staff for internal use. Conversion of the current databases is required. Describe the methodology proposed for converting the current operational and archived NCCCS data to the proposed product suite. The vendor must identify the tool(s) available, if any, with the software product to automate the initial data conversion process from the PI/Open or Universe databases on the IBM under AIX or Sun Microsystems under Solaris operating at 57 of the 59 colleges and the VSAM-based files on IBM mainframes at two colleges. Vendor must describe the strategy for converting the databases at the 59 colleges. Include the cost for conversion and if there is an additional charge for tool(s), include cost in cost model. It is important for the NCCCS to determine the level of application support staff needed to implement and support the proposed application suite. Describe the NCCCS FTE staffing that will be required to implement the product suite in the 59 institutions of the NCCCS and the system office. Refer to the appendix listing the current FTE numbers of technical support staff at each college. List the cost for each option. The vendor must provide a case study of a previous customer with a conversion of similar magnitude. This case study would include the environment customer was converting from, volume of data converted, services provided, vendor consultant effort and cost, effort required by customer staff and time period to complete. Please refer to the Technical Specifications Descriptions for additional information. A Please refer to the Technical Specifications Descriptions for additional information. A 4.23.4 Please refer to the Technical Specifications Descriptions for additional information. A 4.23.5 4.23.6 A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A 4.23.7 Please refer to the Technical Specifications Descriptions for additional information. A 4.23.8 Please refer to the Technical Specifications Descriptions for additional information. A Page 15 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.23.9 4.23.10 4.23.11 Several applications will have to be custom developed by the vendor under the management of the NCCCS including the following information systems: Curriculum Common Course Library, Curriculum Standards, Curriculum Program Design and Approval, Corrections Education Reporting, Literacy Education, Human Resource Development, Small Business Center, Fire Certification, Developmental Education Reporting, Program Auditing, and New and Expanding Industry. The descriptions of these systems can be found on the NCCCS web site, www.ncccs.cc.nc.us, under "documentation". Describe the method and cost of your developing these applications. Significant customization of the standard package will be required to enable reporting information off the college systems to the state level. The requirements for reporting are documented on the NCCCS web site, www.ncccs.cc.nc.us, under the "Documentation/System Office Reporting" and "Reports" sections. Describe the method and cost of your developing these reports. A project of this magnitude will require changes as it progresses. The vendor must propose a budget for changes and a plan to manage change. Software Maintenance and Support The vendor must include the costs of the software update service in the cost model. The cost should take into consideration that software updates will be sent to NCCCS and that NCCCS will then duplicate and vendor must describe any type The distribute to member colleges. of enhancements to their product that are not covered under the normal annual costs. Technical and application support must be available for all software packages acquired from the vendor. Vendor must describe each support plan available for the following areas: All support calls will be placed by NCCCS, however, vendor may be required to access member colleges processor(s) to correct problems. Coverage is needed on a 7 x 24 basis, with prime shift being 8:00am to 5:00 EST/EDT. Proposed turn around time for problems, where NCCCS determines severity of problem - Critical problem - Serious problem - Other problem Escalation procedures to resolve critical and serious problems. Please refer to the Technical Specifications Descriptions for additional information. D Please refer to the Technical Specifications Descriptions for additional information. D A Please refer to the Technical Specifications Descriptions for additional information. 4.24 4.24.1 A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.24.2 4.24.3 4.24.4 4.24.4.1 A A A A 4.24.4.2 4.24.4.3 A A 4.24.4.4 A Please refer to the Technical Specifications Descriptions for additional information. Page 16 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating A Vendor Reference Evalua- Raw Score tion Score Extended Score 4.24.5 4.24.6 Vendor must provide any additional costs for third party software maintenance and support services that are not otherwise specified. Vendor must describe their Support (Help) Desk Structure, including: Levels of Support (first line that take calls and responds/solves the more routine questions and/or Problems, second line for more complex and/or technical questions/problems); current staffing at each level; method of tracking calls with resulting actions; call escalation procedures; availability of solutions database and other relevant information. It is desirable that the NCCCS's Support Analysts have access to the vendors solutions database. The preferred method for access is via the Internet, with dial-up access being acceptable. The purposes of this access is to decrease calls to the vendor and improve services to the colleges. If such access is possible, vendors should so declare and include any one time and/or annual costs associated with this access in the cost model. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A 4.24.7 Please refer to the Technical Specifications Descriptions for additional information. A 4.25.0 NC Information Recourse Management Commission Technical Architectural Requirements The Technical Capability Table provides the requirements of the N.C. Statewide Technical Architecture. Offerors are required to complete the Table as part of their response The offeror must use this table in their proposal to document their proposal’s capabilities for this functional area. (Please note that a synopsis of the Statewide Technical Architecture Standards is listed in this table. A more thorough description of the requirement and can be found in the NC Statewide Technical Architecture (STAD) document). 4.25.1 Application Architecture: Design Manageable Applications: All applications deployed must be designed to be managed by SNMP. Application Architecture Design 3-Tier N-Tier applications Applications should be designed to have a 3-tier architecture separating UI, Business Rules and Data Access logic. N-tier architectures with Business Rules implemented as componentized services is preferred A Please refer to the Technical Specifications Descriptions for additional information. 4.25.2 4.25.2.1 A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A Page 17 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.25.2.2 4.25.2.3 4.25.3 4.25.3.1 4.25.3.2 4.25.4 4.25.4.1 4.25.4.2 4.25.5 4.25.5.1 Design services called by multiple applications (shared services) using the State Service Broker middleware API (Candle's Roma BSP V2.0 or higher) Isolate customizations to purchase software packages to ensure that updates to a new version of the purchased software package does not require recoding of the customizations. Network Architecture: Local Area Network (LAN) Architecture: The standard for LAN cabling is Category 5, 6, or 7 Unshielded Twisted Pair. Ethernet IEEE 802.3 Carrier Sense Multiple Access/Collision Detection Access Method Standard (CSMA/CD). Wide Area Network Architecture: Protocol TCP/IP. Obtain Domain Name System (DNS) and IP address assignments from Information Technology Services. Data Architecture: Conform to NC GILS Standard. A comprehensive database inventory with complete data definitions and descriptions is required. Information about each data element must be provided as described in the “Federated Data Database Registration Worksheet” (See Addendum 3 Exhibit E) . Conform to NC Public Records Law. A comprehensive database inventory with complete data definitions and descriptions is required. Information about each data element must be provided as described in the “Federated Data Database Registration Worksheet” (See Addendum 3 Exhibit E) . (The selected vendor will be required to complete the Worksheet in order to comply with the NC GILS Standard/NC Public Records Law.). Data Architecture: Database Management System (DBMS) Use relational databases that support ANSI Standard SQL. The system must perform all data updates to the authoritative sources only. The system must not allow updates on replicated data. Replication must be from authoritative sources only. Data Architecture: Conform to Federated Data Standard Definitions. Conform to Federated Data Definition Standard for date fields.: The date must be numeric and in a CCYYMMDD format. Componentware Architecture: D Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A A A A A A A A D 4.25.5.2 Please refer to the Technical Specifications Descriptions for additional information. D 4.25.5.3 4.25.6 4.25.6.1 4.25.6.2 4.25.6.3 4.25.7 4.25.7.1 4.25.7.2 4.25.8 D A A A A A D D A Page 18 of 23 Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions to the Technical Specifications Please refer for additional information. Descriptions to the Technical Specifications Please refer for additional information. Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating A A Vendor Reference Evalua- Raw Score tion Score Extended Score 4.25.8.1 4.25.8.2 4.25.9 Use portable, platform-independent language(s) for shared services. Purchased applications that use an object request broker must be CORBA and IIOP compliant. Application Communication Middleware Architecture: Use of the State's service broker is required for inter-application communication because of the lack of standards in inter-application communication middleware. Groupware Architecture: Infrastructure Content ExchangeContent exchange standard file formats (See table 7-2 content exchange standards in the State Technical Architecture). Groupware Architecture: Communication Electronic Mail (Email): Simple Mail Transport Protocol (SMTP) Multi-purpose Internet Mail Extensions (MIME) Internet Message Access Protocol version 4 (IMAP4). Lightweight Directory Access Protocol (LDAP). Groupware Architecture: Use ODMA, DMA compliant products for Document & Content Management Use XML compliant products for Document & Content Management The NC Government Information Locator Service (GILS) State Public Records Cataloging Services Implement workflow systems that conform to the interface specifications of the Workflow Management Coalition (WfMC) Use Adobe Acrobat Portable Document Format (PDF) for NonEditable Electronic Documents Content ManagementEnsure hardware/software and image file compatibility using TWAIN, ISIS, and TIFF standards Select magnetic storage subsystems that adhere to state convenience contract specifications. Select optical storage subsystems based on smaller standard form factors Use eXtensible Markup Language (XML) when capturing or authoring document content that requires further automated processing by other information systems and web-based clients using standard XML enabled browsers. A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.25.10 A Please refer to the Technical Specifications Descriptions for additional information. 4.25.11 4.25.11.1 4.25.11.2 4.25.11.3 4.25.11.4 4.25.12 4.25.12.1 4.25.12.2 4.25.12.3 4.25.12.4 4.25.12.5 4.25.12.6 4.25.12.7 4.25.12.8 A A A A D A A A D D A A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.25.12.9 A Page 19 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.25.13 4.25.14 4.25.15 4.25.15.1 4.25.15.2 4.25.15.3 2.45.15.4 4.25.16 4.25.16.1 4.25.16.2 4.25.16.3 4.25.16.4 4.25.16 4.25.17 4.25.17.1 4.25.17.2 4.25.18 4.25.19 Groupware Architecture: Directory Services The directory service the application uses for authentication must be either LDAP (V3.0 or higher) enabled or NDS aware. Implement LDAP version 3 or higher Information Architecture: Business Intelligence Tools Use relational database that support ANSI Standard SQL. Use ODBC for data access instead of vendor-specific tools. Implement a server based ODBC solution. Use domain name system (DNS) names for databases that are accessible via TCP/IP. Platform Architecture: Server Platform Architecture: Run servers on open operating systems. Make sure platforms are POSIX compliant. Make sure platforms comply with third party certifications. Use Novell Netware on LANs. Ensure physical security and availability of all application servers. Platform Architecture: Client Platform Architecture Platforms must comply with third party certifications. Use PDF417 coding standard for two-dimensional Bar Codes. Platform Architecture: Use operating systems that support a 32-bit or greater processing. Integration Architecture: Electronic Data Interchange Use ANSI X12. Integration Architecture: Clearly define application interfaces. Systems Management Architecture: Operations Management: Use SNMP protocols. D Please refer to the Technical Specifications Descriptions for additional information. D A A A A A A A A A A A A A A A A A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.25.20 4.25.21 4.25.21.1 Page 20 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating A A Vendor Reference Evalua- Raw Score tion Score Extended Score 4.25.21.2 4.25.21.3 4.25.22 Use RMON products. Conform to the DMI standard. Application Communication Middleware Architecture: Access N-tier Services via the Service Broker Use of the State's service broker, Candle's Roma BSP product, is required for inter-application communication because of the lack of standards in inter-application communication middleware. System Management Architecture: Ensure reliability and availability of all servers. Systems Management Chapter: Identification and Authentication: Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. A 4.25.23 4.25.24 A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions to the Technical Specifications Please refer for additional information. Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.25.24.1 4.25.24.2 4.25.24.3 4.25.24.4 4.25.24.5 4.25.24.6 4.25.24.7 4.25.24.8 4.25.24.9 4.25.24.10 4.25.24.11 Authenticate users prior to accessing services Use token-based or strong password based identification & authentication. Public Key Certificates (X.509v3). State Bureau of Investigation standards for live scan fingerprint capture and transmission. ISO 7816 Smart Card standards for contact smart cards. ISO 14443A and Mifare Smart Card standards for contactless smart cards. Use PKCS#11 or PC/SC for integration of smart cards and host/reader-side applications. Speaker Verification API (SVAPI). Human Authentication API version 2.0 (HA-API). Use Public Key/Private Key technology for authentication when digital signatures are required. Avoid proprietary smart card reader-side APIs. Security Standards for E-Commerce. A A A A A A A A A A A 4.25.25 4.25.25.1 4.25.25.2 4.25.25.3 Systems Management Chapter: Access Control: Place Internet application and access services on the DMZ or proxied from the DMZ. Secure transmission of data where appropriate. Secure Sockets Layer version 3 (SSLv3). A A A A Page 21 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating A A A Vendor Reference Evalua- Raw Score tion Score Extended Score 4.25.25.4 4.25.25.5 4.25.25.6 4.25.26 4.25.26.1 4.25.26.2 4.25.26.3 4.24.27 4.24.27.1 4.24.27.2 4.24.27.3 4.25.28 IP Protocol security extension (IPsec). Cryptography must be based on open standards. Use S/MIME version 3 for securing email communications. SECURITY CAPABILITY STANDARDS TABLE Control user access to vendors software modules by a single login password, id and role-based authentication. Archive access and violation logs Permit custom developed applications to be tied to the standard application security. Support security profiles for users or multiple groups of users which control: Which modules including integrated third party applications and functions can be accessed What tables can be read, changed, created, or deleted by a particular user or group of users What data within tables can be read, changed, created, or deleted, by that particular user or group of users Detect a specific number of unsuccessful attempts and prevent further access until a system administrator has verified that the user is authorized to enter the system. ADDITIONAL TECHNICAL REQUIREMENTS : Year 2000 The software must perform fault-free in the processing of date and date-related data (including, but not limited to, calculating, comparing, and sequencing) by all hardware, telecommunications, and software products delivered under this contract/procurement, individually and in combination, upon installation. Fault-free performance includes the manipulation of this data with dates prior to, through, and beyond January 1, 2000, and shall be transparent to the user . Hardware, telecommunications, and software products, individually and in combination, shall successfully transition into the year 2000 with the correct system date, without human intervention, including leap year calculations. Hardware and software products, individually and in combination, shall also provide correct results when moving forward or backward in time across the year 2000. ADDITIONAL TECHNICAL REQUIREMENTS PART TWO A A A A A A A Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. Please refer to the Technical Specifications Descriptions for additional information. 4.25.29 A 4.25.30 Please refer to the Technical Specifications Descriptions for additional information. A Page 22 of 23 Sec. 4. Item Number North Carolina Community College System -Technology Specs for RFP Item Description Vendor Availability Rating Vendor Reference Evalua- Raw Score tion Score Extended Score 4.25.31 The software must perform fault-free in the processing of date and date-related data (including, but not limited to, calculating, comparing, and sequencing) by all hardware, telecommunications, and software products delivered under this contract/procurement, individually and in combination, upon installation. Fault-free performance includes the manipulation of this data with dates prior to, through, and beyond January 1, 2000, and shall be transparent to the user. Please refer to the Technical Specifications Descriptions for additional information. A Page 23 of 23