This document summarizes Hal Kinsey's internship projects at GSA from May to August 2016. It describes 9 priority projects including developing automation bots to pull customer reports and billing data from databases to save time. It also covers side projects interviewing employees and training teams on Skype. The conclusion reflects on lessons learned about work ethic and time management and provides suggestions such as improving collaboration and investing longer-term in the company.
I am Murali.Below is a short summary on my professional experience,
Total years of experience - 13 (Releavant BO experience - 10 Years)
Technologies/Tools worked on : SAP BO 4.x - XI R2,BO Admin, Xcelsius Dashboard designing, Crystal Reports, SAP Design Studio, SAP BW 7,Unix,Oracle 10G PL/SQL, SQL Server and Microsoft Technologies(VB,ASP and VB.Net).
I am interested to take up new roles on different aspects in BO domain.
IT Professional with 9 years of Data Warehousing experience in the areas of ETL design and Development.Excellent Experience in Requirement Gathering, Designing, Developing, Documenting, Testing of ETL jobs and mappings in Parallel jobs using Data Stage to populate tables in Data Warehouse and Data marts.
As we all know, more and more organizations are starting to question “Do we or do we not implement Office 365?”. However, as these discussions are taking place; governance is rarely addressed or considered. The main reason is that the majority believe that once they have implemented governance that they are done; unless there is an update such as a server name change or an employee change (such as a departure or addition). During the initial planning around governance it is likely that there were discussions around auditing of the governance document and potential quarterly reviews to ensure that the document is up to date and still fits the business. However, it is common to forget that after that fact; even though it is documented “within the governance document”.
Governance becomes even more important with Office 365 just because its cloud based and ever changing with new and deprecated features on a pretty regular basis. This means all of the content, backup, recovery, etc. are all handled by Microsoft and you have virtually no control over it (Can you say MAJOR SLA impact?). In this session we will review the areas of concern and how they can be addressed within the governance document, the importance of reviewing the document frequently; and ways to make the information available to your internal SharePoint Community. In addition, we will review the features of Office 365 that will have a major impact on SharePoint and Office Apps. We will review each of these applications and the areas of importance that should be addressed in the governance document, as well as why each of them are important.
I am Murali.Below is a short summary on my professional experience,
Total years of experience - 13 (Releavant BO experience - 10 Years)
Technologies/Tools worked on : SAP BO 4.x - XI R2,BO Admin, Xcelsius Dashboard designing, Crystal Reports, SAP Design Studio, SAP BW 7,Unix,Oracle 10G PL/SQL, SQL Server and Microsoft Technologies(VB,ASP and VB.Net).
I am interested to take up new roles on different aspects in BO domain.
IT Professional with 9 years of Data Warehousing experience in the areas of ETL design and Development.Excellent Experience in Requirement Gathering, Designing, Developing, Documenting, Testing of ETL jobs and mappings in Parallel jobs using Data Stage to populate tables in Data Warehouse and Data marts.
As we all know, more and more organizations are starting to question “Do we or do we not implement Office 365?”. However, as these discussions are taking place; governance is rarely addressed or considered. The main reason is that the majority believe that once they have implemented governance that they are done; unless there is an update such as a server name change or an employee change (such as a departure or addition). During the initial planning around governance it is likely that there were discussions around auditing of the governance document and potential quarterly reviews to ensure that the document is up to date and still fits the business. However, it is common to forget that after that fact; even though it is documented “within the governance document”.
Governance becomes even more important with Office 365 just because its cloud based and ever changing with new and deprecated features on a pretty regular basis. This means all of the content, backup, recovery, etc. are all handled by Microsoft and you have virtually no control over it (Can you say MAJOR SLA impact?). In this session we will review the areas of concern and how they can be addressed within the governance document, the importance of reviewing the document frequently; and ways to make the information available to your internal SharePoint Community. In addition, we will review the features of Office 365 that will have a major impact on SharePoint and Office Apps. We will review each of these applications and the areas of importance that should be addressed in the governance document, as well as why each of them are important.
2. Hal Kinsey – GSA Intern
Employment Period:
May 23rd – August 5th
Chain of Command:
Hal Kinsey Marla Cruse Angela Cullen John Klebonis
2
3. Projects (In Order of Priority):
CSR Bot
Scope:
• GSA PMO and Care Centers
Task Description:
Develop an automation capable of pulling
Customer Service Reports (CSR) from Business
Objects with all necessary information.
Purposes/Problems:
• Current reports not adequate
• No known process to acquire information
Problem Solving Process:
• Documented entire process
• Gained access to necessary databases
• Investigated alternative solutions
• Discussed with experts
Resources Utilized:
• Team members
• Outside departments
• Business Objects
• Rapid Applications
• Automation Anywhere
Status:
• Developed alternative solution
Estimated Savings:
• $10,000/year
3
4. Projects (In Order of Priority):
WBS (Work Breakdown Structure) Calculator
Scope:
• Entire GSA PMO
• Replicable for other organizations
Task Description:
Using common task dependencies, task durations, and a
start date, create a spreadsheet that calculates
estimated completion dates for project milestones.
Purposes/Problems:
• Used for customer reference
• Dates being calculated by hand
Problem Solving Process:
• Built task dependencies
• Created function that excluded weekends and
holidays from duration calculation
Resources Utilized:
• Team members (Laurie Johnson)
• Microsoft Excel
• SharePoint
Status:
• Completed
• Potential users in GSA trained
• Used for four different projects
Estimated Savings:
• $20,000/year
4
5. Projects (In Order of Priority):
Order Summary
Scope:
• GSA PMO and Care Centers
Task Description:
Create a spreadsheet that consolidates and
standardizes GSA order tracking throughout
all regions.
Purposes/Problems:
• Formatting not consistent
• Compare sales/order activity across
regions
Problem Solving Process:
• Organized existing information
• Created template
Resources Utilized:
• Team members
• Microsoft Excel
• SharePoint
Status:
• Completed
• Users trained
Benefit:
• New reporting capabilities
5
6. Projects (In Order of Priority):
SOC Report Bot
Scope:
• Developed for Region 9 (CA, AZ, & NV)
• Replicable in other regions
Task Description:
Build an automation that pulls SOC reports for
Region 9 and transposes the information to
sheets that can be safely accessed by the
customer.
Purposes/Problems:
• Certain contracts require weekly updates
• Eliminate tedious, time consuming task
Problem Solving Process:
• Documented entire process
• Gained access to necessary databases
Resources Utilized:
• Team members
• Outside departments
• Microsoft Excel
• Automation Anywhere
• SharePoint
Status:
• Completed
• Runs weekly for Region 9
Estimated Savings:
• $2,000/year for Region 9 alone
6
7. Projects (In Order of Priority):
GSA Metrics
Scope:
• GSA PMO and Sales teams
Task Description:
Create a unique method for reporting various
forms of GSA data.
Purposes/Problems:
• Information not compiled in one location
• Modernize GSA data reporting
Problem Solving Process:
• Acquired necessary pieces of data
• Gained access to necessary databases
• Built graphic with hyperlinks
Resources Utilized:
• Team members (Karen Richter)
• AT&T Brand Center, tSpace
• Microsoft PowerPoint, Excel, & Word
Status:
• In progress
7
8. Projects (In Order of Priority):
Thrifty Bill Bot
Scope:
• Collections
• Billing Support Managers
• Sales
Task Description:
Build an automation that analyzes thrifty accounts
in multiple scrub databases and returns an output
identifying the account discrepancies.
Purposes/Problems:
• Accounts not being billed correctly
• Extremely time consuming task
Problem Solving Process:
• Documented entire process
• Gained access to necessary databases
• Spoke with RPA experts
Resources Utilized:
• Team members
• Outside departments
• ROAR
• Microsoft Excel, Notepad
• Automation Anywhere
Status:
• Completed
Estimated Savings:
• $43,560/year
8
9. Projects (In Order of Priority):
AHC Charges Capture
Scope:
• GSA PMO
Task Description:
Build an automation that pulls and tabulates
customer charges for various services.
Purposes/Problems:
• Calculate total charges for customers
• Eliminate tedious, time consuming task
Problem Solving Process:
• Documented entire process
• Gained access to necessary databases
• Spoke with RPA experts
Resources Utilized:
• Team members (Terri Ryals)
• Outside departments
• DocViewer
• Microsoft Excel
• Adobe PDF
• Automation Anywhere
Status:
• In progress
9
10. Side Projects
Interviews
Task Description:
Conduct interviews with 10 AT&T employees.
Purposes:
• Learn more about the diverse functions and
growing capabilities of AT&T
• Identify strengths stemming from various
knowledge backgrounds
• Develop a network
Method:
• Organized meetings with co-workers
• Utilized new Workspace 2020 meeting
spaces
10
Benefits:
• Understand value of various knowledge
backgrounds
• Learned about the vast opportunities at
AT&T
• Developed network for both work here and
future employment
11. Side Projects
Skype for Business Borderless Collaboration
Task Description:
Learn about and train team members on the
Skype for Business tool.
Purposes:
• Create comfortable transition into new
communication tool
Method:
• Assembled detailed PowerPoint
• Skype for Business training call on Skype for
Business
11
12. Conclusion
What I Have Learned/Observed:
• Extremely strong work ethic
• Time-management skills
• Benefits of networking
• Positive work environment
12
13. Suggestions
What is Being Done Well:
• Availability of tools
• Workplace satisfaction
• Intra-organization collaboration efforts
What Needs Improvement:
PCSC:
• More external assistance with automation
• Budget for face-to-face meetings
• Intra-organization collaboration
FLITE:
• Organize resources/interns more appropriately
AT&T:
• Inter-organization (AT&T) collaboration efforts
• Invest more long-term within the company
13