The groups and teams that make up the Office of IT support our vision of an integrated, enterprise-wide IT ecosystem for The Texas A&M University System, one that serves the full spectrum of institutional needs, from strategic leadership to day-to-day operations.
System Enterprise Applications (SEA)
SEA’s approach emphasizes thoughtful evolution: advancing enterprise capabilities while stewarding existing systems, reducing technical debt, and making data-informed, context-aware decisions. Through collaboration, strategic analysis, and investment in our people, SEA works as one team to sustain, modernize and strengthen the systems that enable efficient operations and meaningful impact across the system.
As our planning and reporting continue to evolve, this view will expand to include additional details such as upcoming work, timelines and dependencies. Please note that projects are listed at the SEA unit level to emphasize enterprise outcomes and shared responsibility. We may add team-level details in future iterations as additional project context is introduced.
| Project | Description |
| FAMISweb development and implementation | Development of the modernized Financial Accounting Management Information System (FAMIS) interface to replace Canopy and some 3270 features. FAMISweb will be a new web-based application built on modern infrastructure, featuring an updated design, improved navigation and enhanced functionality. FAMISweb will provide a better user experience. Additionally, we will address some layers of the technical/backend to reduce technical debt and improve the performance and stability of the customized codebase. SEA is currently collaborating with two external partners on this work, Avanade and Capsher Technologies. Ultimately, our goal is to build out FAMISweb to replace Canopy and much of the functionality in the FAMIS 3270 “green screens” by the end of calendar year 2026. |
| TEEX to FAMIS conversion | The Texas A&M Engineering Extension Service (TEEX) is one of only two A&M System members not currently using the system’s financial and accounting management information system platforms, FAMIS and Canopy (soon to be replaced by FAMISweb). This project includes the work required to convert TEEX to FAMIS and related applications and to integrate with certain TEEX applications and programs. |
| Disaster recovery (planning and exercise) | This initiative focuses on establishing and maintaining documented disaster recovery plans for mission‑critical information resources to support continuity of operations and institutional resiliency. Work includes identifying recovery objectives, roles, dependencies and required resources, ensuring that plans align with A&M System information security and availability requirements. We will schedule a formal disaster recovery exercise (e.g., tabletop or functional) to validate preparedness and use the results to inform plan updates and future risk mitigation activities. |
| AggieBuy to FAMISweb integration assessment | AggieBuy is a web-based e-Commerce system developed by Texas A&M University, in partnership with JAGGAER. Customers may browse and shop from numerous online catalogs and Texas A&M Contracts, or place orders to virtually any supplier through a “non-catalog/non-contract” requisitioning process, and more. Invoices and payment requests are initiated and created within AggieBuy, which fully integrates with FAMIS. This initiative will assess the integrations between AggieBuy and FAMIS/FAMISweb (and some AggieBuy-specific configurations) to identify opportunities for modernization and operational efficiency. |
| Cadency implementation | Cadency is the updated product replacing TRECS. Guided by an external partner team, this work will help provide a better understanding of the current state processes of appropriation and fund-level USAS (and other) reconciliations for representative members of the A&M System. That understanding and review will then inform the design, which will include process optimization opportunities, key requirements, and an operationalized project plan for TAMUS members to expand their use of Cadency with this reconciliation tool. |
| Emburse expansion | Following the initial rollout of Emburse in late spring 2025, this effort addresses several approved scope expansions to support additional reimbursement and travel needs. Work includes accommodating Athletics’ travel agency changes, enabling a voucher-based reimbursement option for nontravel expenses and resolving outstanding financial processing issues to ensure accurate closeout of transactions. These updates will improve usability, reduce manual workarounds and better align Emburse with existing financial processes. |
| FAMISweb Fixed Assets (FFX) module reimagination Includes FAMISweb FFX transaction history improvements |
As part of the FAMISweb implementation and development, the entire fixed assets module is being completely reimagined and rewritten. Given the scope and impact of this work, we are listing it separately, although it is closely related to the FAMISweb work in general and to the Radiant RFID implementation. The team is also working on improvements to the FFX transaction and history tables as part of the overall modernized asset maintenance processes. |
| GitHub source control migration | This migration of the System Enterprise Application team’s source code from Azure DevOps to GitHub Enterprise is a required prerequisite to two future security-related projects: Application Dependency Vulnerability Scanning/Remediation and Source Code Secret Scanning/Remediation. The migration is required because GitHub’s built-in support for these functions is years ahead of what Azure DevOps offers. As a whole, these three projects are foundational to improving the security of our code, particularly in the supply chain, for our custom applications such as FAMIS, Single Sign On, FAMISweb, Position Budgeting, TrainTraq and many others. |
| HighRadius expansion | HighRadius was first implemented with the Texas A&M University Financial Management Office (FMO) in 2024 for a subset of system members. HighRadius provides enterprise-level, automated accounts receivable processes including collections, customer self-service payments and invoice presentment. The 2026 expansion will roll out HighRadius to five additional system members. |
| ID.me implementation | The implementation of ID.me in Single Sign On (SSO) replaces the UIN login for all “nonactive” employees: pre-hires, retirees, benefit dependents and former employees. The ID.me implementation is part of the larger UIN login replacement project, which began with removing the UIN login for active employees. |
| Insurance Billing (SBA) modernization | Created internally and launched in December of 2020, this application manages the payment of insurance premiums for retirees and other nonemployees who use A&M System insurance. It integrates FAMIS, Teacher Retirement System (TRS), and Wells Fargo; provides a user interface for the benefits department; and produces invoices. This initiative will move the application to a more modern infrastructure for better performance and compatibility with our other financial systems components. |
| Position Budgeting Application (PBA) modernization | Created internally and launched in 2018, this application supports the budget process by enabling planning and costing for all positions for the next fiscal year. Similar to the SBA modernization, this initiative will move the application to a more modern infrastructure for better performance and compatibility with our other financial systems components. |
| RadiantRFID implementation | Provides for an effective automated asset-tracking system, improving search capabilities and more. This implementation will integrate asset location information into FAMISweb, helping our members realize and maintain an up-to-the-minute asset inventory. |
| Snowflake: A&M Foundation endowment data | Provides a cloud-native data cloud platform for multiple “data” services: warehousing, data lakes, data engineering and data science. This project aims to establish a data pipeline to securely transfer endowment data from the A&M System’s FAMIS Enterprise Data Warehouse (EDW) to Snowflake (leveraging Informatica) for data integration, in particular, while also laying the foundations for future projects using these technologies.
Additionally, the teams are actively working on two other major initiatives with Snowflake: |
| SSO Duo implementation and updates | Duo implemented security changes in 2026, including expiring key security certificates that require mandatory Duo Mobile app version upgrades and ending support for older versions of iOS and Android. This project is mostly about communicating with SSO UIN login users, some of whom will be adversely affected if they fail to upgrade on time. Note that in some cases, older smartphones used by our users will not support the required upgrade, and they will lose access to Duo Mobile push notifications until they replace the device. |
| US Bank integration and data source | Due to the State of Texas banking transition, this initiative updates financial integrations and reporting to align with US Bank requirements. The work ensures credit card activity continues to flow correctly into FAMIS and downstream reporting systems, supporting accurate tracking and analysis. Additional updates focus on improving the completeness and consistency of credit card data available for enterprise reporting. |
| Workday integration: time-off balance (WD INT009) | This replacement of Workday’s time off balances integration will provide additional data to Business Objects, as required by the System Office of Budgets and Accounting. Specifically, the integration will now provide time-off balances for employees with existing balances who are no longer eligible to accrue leave. Additionally, the future integration will significantly improve performance, which has been very poor to date. |
| Workday integration: worker change-data completeness/timeliness | This replacement of Workday’s daily worker update to SSO allows SSO to receive near-real-time updates to employees’ status, name, contact information and other data elements. The speed and breadth of the new integration will improve both our user support and data security postures. Currently, most employee data updates require an overnight integration to arrive in SSO, while a handful arrive every two hours. |