Questions and Concerns About the eUP Project

This community page is created and occasionally revised on "best effort basis" to help advance the University's interest and goal of operational excellence via the eUP Project. UP constituents with UP Webmail accounts can directly modify this page. Special access can be requested (via Helpdesk) by UP constituents who don't have UP Webmail accounts. UP constituents may also post their concerns via social media (see instruction below).

Accountability

• Project design and planning

• Implementation

• Evaluation

Technical Details

Network

• Latency. eUP servers will be hosted by PLDT's Vitro Data Center. UP networks are on PREGINET. They are wide apart in terms of the routes they'd take to reach each other. The same holds with connections between ePLDT and other providers. See traceroutes below. This is an issue when it comes to UP's access to its own data. User authentication is potentially problematic due to delays.

traceroute from PREGINET to PLDT's Vitro Data Ctr. Notice the spikes on hops 6 and 7.

traceroute from Bayantel to PLDT's Vitro Data Ctr

eUP Team's Response

• Data Migration.

eUP Team's Response:

• Authentication Authorities. Authenticating centrally or by CU?
  
  

eUP Team's Response:

Budget

• Continuity of project. From which unit will the MOOE come from after the project has concluded/closed?
  
  

eUP Team's Response

---

Social Media

Other discussions may be posted via Facebook and Twitter.

• Twitter: please post with hashtag #eUPWatch

---

References

• Ronald S Banzon, 2012. "EUP Implementation in UPD-Concerns" (presentation)
• "Questions and Concerns About the eUP Project" (a compilation of questions and concerns from the different UPD units; publicly distributed at the eUP Kickoff in UPD, 6 Aug 2012)

See Also

• Issues in cloud computing and storage