Previous Job
Infrastructure Project Manager
Ref No.: 17-16302
Location: Chantilly VA, Virginia
Position Type:Contract
Start Date: 05/17/2017
Client WMATA
Job : Infrastructure Project Manager
Location : Jackson Graham Building Washington, DC
Duration : Long Term Contract

Job description:-
1. Working with the Program Manager, Deputy Chief of ITNCS, and Mid-Shift WIG Manager for Rail Station wireless project, coordinate and manage the track rights, escorts, equipment, and work plans for Rail Station Wireless project work.
2. Analyze vendor requests for work access and translate into rights and access as
required to accomplish the work and maintain safety in accordance with WMATA safety policies.
3. Conduct site surveys at each rail station to determine the best paths for conduit runs.
4. Work with wireless engineer to determine optimal placement of wireless access points.
5. Develop build of materials for supplies and tools required to perform all installation and testing activities.
6. Generate track rights / manage workflow process for track rights. Knowledge of WMATA track rights scheduling a plus. 7. Leverage knowledge of safety procedures to ensure access, escorts, and work plans meet all applicable safety protocol. 8. Leverage knowledge in planning and constructing Communications systems in an underground subway system to assist the

contractor in optimizing their work and access requests.
9. Leverage understanding of rail operations to coordinate rail equipment and personnel in support of the contractor's work.

Supplemental Duties:
Respond to Network Operational Issues The ability to define, communicate, maintain ownership and resolve Network Problems
1. The ability to communicate the definition of the problem to the client, NOC, colleagues and supervisors and to keep them updated. Your communications should be written in a fashion that adequately conveys the definition of the problem and what steps you are taking to address it. The updates should provide enough information for recipients to understand the network operational issue.
2. For problems that are multi-faceted, and thus involve other groups (i.e., servers, desktops, cable runsetc), the ability to maintain ownership of the "network " component of the issue. As owner of the issue it is your responsibility to see that the issue is remediated to its final conclusion in all aspects that involve Company responsibilities. If the issue is clearly not an Company responsibility, you must be able to define why it is not and to make sure that they client is aware of this fact by email. Within the scope of Company responsibilities, it your responsibility to seek out resources if resolution of the issue is beyond your skill set and or means by informing your teammates and supervisor of this fact in a timely fashion.
3. The ability to willingness to engage other groups and reach out to end users for problem definition and coordinated troubleshooting. You need to demonstrate your ability and willingness to communicate and work with other non-Company groups in the resolution of issues by email, phone and in person when the situation warrants it. For example, many reported issues may have a component that involved IT security. It is expected that you can work with a group like this to define the problem, narrow down the issue and resolve it.
4. In the performance of this goal, deliver quality service, use every resource wisely and maintain and enhance Metro's image. Network Projects/Provisioning When assigned as the
lead for a network project or provisioning request, design and implement network engineering technologies and configurations to solve problems needing network engineering solutions. Design and implement network electronics to solve customer network provisioning needs such as new end hosts and systems. 1. It is expected in the delivery of this responsibility that you can write a network project document that defines a number of critical items as follows and to gather and report this information. The Network Project Document should: a. Define the problem or task that is the reason for the network technology solution. b. Define the end user requirements in a thorough and understandable manner. c. Define the scope of the work. d. Identify dates and expectations. e. Identify Point of contacts from both the Company and customer side. f. Identify other non-Company groups that are part of the solution and what their roles are. g. Identify any infrastructure issues or requirements that are critical for the completion of the work. h. Identify any other issues that are critical or must be overcome for the completion of the work. i. Include a network topology of the existing architecture. j. Include a network topology of the proposed architecture. k. Define the network electronics and materials such as cables and fiber needed to fulfill the solution. l. Define costs associated with the network electronics and materials needed to fulfill the solution. m. Identify the port counts needed to fulfill the solution. n. Identify the VLAN and IP subnets to be allocated. o. Include any voice requirements and backup plans for voice. p. Include a migration plan that details the steps needed to move from a before to an after scenario. This plan should provide enough detail that demonstrates how the solution can be implemented successfully.
2. It is expected that you can develop a provisioning script and/or step by step procedure that details the implementation process and that this script is inclusive of all steps necessary to accomplish a successful implementation during one or more defined work windows. It is expected that you can lead the execution of the script that may or may not involve other individuals or groups during one or more defined work windows in a fashion that results in the successful completion of the work.
3. When provisioning the network for network business systems and/or applications, it is expected that you can write documentation that accomplishes the following at a minimum: a. You should be able to identify the control plane elements that make up the business systems (control plane elements are defined as servers and applications that communication to with each other.) b. You should be able to identify the server to client and client to server or data plane elements. c. You should be able to identify systems by IP address and DNS host names. d. You should be able to articulate in writing how the control plane operates and how the data plane operates with the goal of understanding and identifying their requirements from the network. e. You should be able to develop Microsoft Visio topology maps that identify the interconnections between network elements both from a layer 2 perspective and a layer 3 perspective.
4. It is expected that you have sufficient knowledge of the network technologies needed to implement the project and that you are able to demonstrate this knowledge in the development of the work script, presentation to others and implementation of the work.
5. It is expected that you are able to submit change control requests that correspond to changes needed to implement the solution and to do so in a manner that adheres to the change control policy. It is important that you include in the CCB submission scripts that detail the work and that you understand the differences between operational and non-operational CCBs and can create them accordingly. The key goal is to execute your work in a manner that does not lead to unplanned network outages.
6. It is expected that you can communicate with the client or end users by email, phone and in person to identify their requirements in a thorough manner.
7. It is expected that you can work with other Company and non-Company groups that have responsibilities in the implementation and planning of the solution in a fashion that accomplishes the following goals: a. Defines roles and responsibilities. b. Defines a timeline for work coordinated work if necessary. c. Develops coordinated implementation scripts.
8. It is expected that you can present your project or provisioning effort to your supervisor, teammates and customers in a fashion that is understandable and meets the goals that are defined in your network project
9. It is expected that you can escalate to your supervisor issues that hinder the successful completion
or progress towards completion of this project when you encounter them so that those obstacles can be removed and thus they do not impact the timeline associated with completing the work. Escalation should occur no later than one hour or close of business that day, whichever is sooner.
10. It is expected that you can create a cost estimate for network electronic provisioning using the Company cost estimate template that is accurate and presentable to our clients