Data Integration. Democracy Suite shall have the ability to import the candidate/contest information directly from the ROV’s DFM election information management system and create the absentee ballot, ICX ballot, and sample ballot from the same imported file. Democracy Suite shall be capable of importing audio and text files.
Data Integration. 7.1 The Contractor is responsible for migrating manufacturing data directly from the cart manufacturing facility to the asset management software that shall be provided by the Contractor to the Town. The data included in the specified file format from the manufacturer needs to include information on each individual cart, including but not limited to, cart size, color, type, serial number, date of manufacture and plant of manufacture.
7.2 Contractor must provide a complete asset tracking/inventory/work order system and data delivery program that seamlessly integrates with the RFID data capture delivery systems provided by the Contractor for reporting data concerning Collections.
Data Integration. Invoice Cloud will maintain integration with Xxxxxx’x utilility billing system, enQuesta, through its partnership with S&S. The integration for S&S will include the following:
a. Real-time data exchange with enQuesta utilizing Invoice Cloud’s (patent pending) Data Pump technology
a. Single sign-on (SSO) between WebConnect customer login and IC EBPP.
Data Integration. Using the Software's standard import and export files, the Institution can move data to and from the EMASPLUS database. It is the responsibility of the Institution to format and prepare the date properly to use the import and export files and achieve data integration.
Data Integration. Invoice Cloud does maintain an integration with Bi-Tek. The integration for Davidson County will include the functionality found in Appendix B.
Data Integration. The Contractor and the Institution shall work together in cooperation, each at its own expense, to accomplish the Institution’s desired level of data integration between the Institution’s SIS and the Contractor’s system(s) to administer the Plan. For purposes herein, a download refers to the transmission of data from the Contractor to the Institution, and an upload refers to the transmission of data from the Institution to the Contractor. At the Institution’s option, levels of data integration to administer the Plan may include but are not limited to:
a. An upload of student enrollment balance information from the SIS system to the Enrollment Site, commonly referred to as a “Web carry along” of student balances;
b. An upload of actual or estimated financial aid awards, scholarships or other amounts credited to the student;
c. An upload of increases or decreases to agreement balances as a result of a process commonly known as “drop and add” prior to the Prefund Date;
d. An upload of credit adjustments (reductions) to agreement balances after the Prefund Date;
e. A download of payment data originating from full payments, down payments and regularly scheduled tuition installment payments from the Contractor’s online system to the SIS; and/or
f. Other points of integration as determined by the parties.
Data Integration. Agency Enterprise Data System
a) Develop a plan and assess our agency efforts to bring all agency databases into one multi-media system. This will include a complete assessment of IDEM’s existing applications and databases (i.e. all major permit/compliance databases). The plan will consider cost, time requirements, and migration impacts on current users. 100% complete. As part of the National Environmental Information Exchange system, IDEM was awarded a Readiness Grant. Plans have been completed to migrate each of IDEM's databases (in phases) into a multi-media system, the Indiana Facility Registry System (I-FRS), which is based upon the assessment. The project's timeline will be extended into the next EnPPA cycle.
b) Develop Place Components of Core Data Model Review the agency’s inventory of place information, document data maintenance, procedures/ rules, develop maintenance application components and migrate existing locational data into the core model. 10% complete. Due to fiscal constraints, this project was slowed. IDEM received a NEIEN Readiness grant from EPA, and the project's timeline will be moved into the next EnPPA cycle.
c) Populate the People/ Organization Components of the CORE Data Model As a part of our agency system, pilot a project to maintain and associate interested parties with OAQ permit decision to ensure that interested parties are properly notified as a permit of interest to them goes through it’s public process by March 30, 2002. 30% complete. Due to fiscal constraints, this project was slowed. IDEM's NEIEN Readiness grant is targeted to bring FRS functionality to the State, as work progresses under this grant award. Timeline will need to be extended.
(1) Develop a web-based application to allow citizens to register and create personal profiles to manage their information requests (print publications, notices, etc.) from IDEM. 10% complete. Investigating zero dollar cost tools that may help us develop this system. Appears to be on temporary hold until fiscal situation changes.
(2) Migrate Facility Linking Application (FLA) Data set to IDEM Core Data Model. 10% complete. Due to fiscal constraints, this project was slowed. As part of the National Environmental Information Exchange system, Indiana received a Readiness Grant to complete this project. The project's timeline will be extended into the next EnPPA cycle.
(3) Develop process to maintain/populate EPA’s systems with IDEM data utilizing our new data system. 100% complete. As...
Data Integration. In the event Customer desires to establish a technical connection between Leanpath Services and a non-Leanpath Customer system to enable a form of data exchange between Leanpath and such system (an “Integration”), Customer shall enter into a standalone Order Confirmation with Leanpath which specifically defines the requirements, timing and cost for such Integration.
Data Integration i. The Contractor shall ensure data integration uses federal standards where applicable.
ii. Contractor shall ensure data Integration is able to perform Service Bus functionality where needed.
iii. Contractor shall use MuleSoft as the API Gateway unless there is a compelling reason not to do so. If Contractor wishes to utilize a different API Gateway, the Contractor must receive approval from the State.
iv. Contractor shall satisfy the following API Gateway and development requirements:
(A) Create conceptual and solutions architecture designs to include the API Gateway and its interactions with ACES and any other source systems.
(B) Use the dedicated API Gateway within the already existing HHS Coalition API Gateway solution.
(C) Configure Product 1 specific configurations on an existing API gateway, while ensuring flexibility to support future IE&E Products and releases, including integration with the IE&E Platform and Coalition Source Systems (e.g., ACES). The Product 1 configurations will initially be supported by the Contractor and then maintained and enhanced by the state Platform team.
(D) Define user roles needed to build, implement, operate, and maintain the IE&E API Gateway.
(E) Identify and document the list of required APIs needed to support the Product 1 team.
(F) Complete design, development, and testing of the required APIs identified in requirement (A) above, working with the HHS Coalition Product and Platform teams.
(G) Implement and deploy the APIs by working with the Product Team and ACES M&O vendor to implement.
(H) Create and publish API documentation including information regarding how to invoke and consume the service.
(I) Design and develop, in collaboration with HSS Coalition teams, operational processes including monitoring and administration requirements for APIs.
(J) Design and configure any required custom dashboards or reports needed in the API Gateway to display performance and usage if not available in the out-of-the-box offerings.
Data Integration. Invoice Cloud maintains an integration with Xxxxxx Cayenta. The integration for the Xxxxxx will include the functionality found in Appendix B, attached hereto. Xxxxxx shall be responsible for providing the items listed in Appendix C: Xxxxxx Deliverables, attached hereto.
