Magnify glass looking over the contents of a folder

Job title: IT Investment Portfolio Manager

 Apply Now

  • Location: Washington, DC
  • Employee Type: Full-Time
  • Industry: Government Consulting
  • Job Type: Information Technology Consultant
  • Education: 4 Year Degree
  • Experience: 5 years
  • Support all phases of CPIC – Select, Control, and Evaluate.
  • Prepare, review and score OMB Exhibit 300 and 53.
  • Develop and deliver IT PfM training.
  • Provide written and oral presentations/briefings to clients.
  • Develop and implement IT portfolio management guidance.
  • Support IT investment governance processes.
  • Support TBM implementation.

Work is at client locations in the Washington, DC area. Ability to obtain U.S. Government security clearance is required.

NISH Consulting is an Equal Opportunity Employer and promotes a corporate environment of diversity. This diversity strengthens our ability to meet the needs of our clients, and ensures equal employment opportunity without discrimination on any basis protected by law.

Click Here to Apply

Magnify glass looking over the contents of a folder

Job Title: Enterprise Architect Apply Now

Location: Washington, DC

Employee Type: Full-Time

Industry: Government Consulting

Job Type: Information Technology Consultant

Education: 4 Year Degree

Experience: Between 4 and 10 years of professional experience


Description

Position is based in Washington, DC and provides technical and analytical expertise within the IT investment management and enterprise architecture programs. Work is at client locations in the Washington, DC area. Ability to obtain U.S. Government security clearance is required.


PRINCIPAL DUTIES AND RESPONSIBILITIES:

Enterprise Architect will be responsible for assisting government client in analyzing and evaluating enterprise architecture and IT investments in support of IT governance. The position requires between 4 to 10 years of experience.

Key responsibilities include:

  • Conduct business and technical architecture analysis
  • Develop business process models
  • Conduct IT investment analysis
  • Develop recommendations to improve IT investment decision-making and related management processes based on strong analytics.
  • Provide written and oral presentations/briefings to clients on results.
  • Extract architecture and investment data from various tools and tailor for presentation to governance councils and other stakeholders at varying levels.
  • Prepare management reports and analysis as required.


Requirements

KNOWLEDGE, SKILLS AND ABILITIES

  • Bachelor’s degree in business or information systems or related fields required. Masters degree and PMP™ certification are highly desirable.
  • Four years work experience, with an emphasis on Business Analysis, Enterprise Architecture, IT investment management, and IT system development life cycle.
  • Experience using IBM Rational System Architect
  • Must be comfortable working in a fast paced and dynamic client/consultant environment.
  • Must be a team player.
  • Proficient use of Microsoft Office suite – excellent skills in PowerPoint and Excel.
  • Strong consulting skills required
  • Strong problem solving and analytical skills.
  • Superior communications skills, both oral and written.

Applicants selected for this position may be subject to a government security investigation.

Click Here to Apply

Posted by Jonah Hatfield on February 21, 2014 at 4:30 PM EST

PortfolioStat is a performance metric, established in 2012, which requires federal agencies to report how effectively they manage their information technology portfolios and expenditures. One portion of the PortfolioStat submission is the Integrated Data Collection (IDC). The IDC collects information on the IT expenditures of an agency in order to identify potential technology savings. This information is then reported to the Office of Management and Budget (OMB). The types of data reported include commodity IT spending, mobile contracts inventories, cost savings and avoidance decisions, etc. As of August 2013, the IDC must be reported to OMB on a quarterly basis, rather than annually.

Executing a data collection process at large government agencies requires the active, direct support of federal employees with strong backgrounds in the individual business lines they support. Since a large portion of the IDC submission involves data not routinely reported by the individual business lines or contained in a central database, points-of-contact within each business line must be contacted individually in order to capture the required IDC data. Agencies have been challenged with automating this process in order to keep the requested data current and readily available for each quarterly submission.

Approach and Methodology

NISH has a structured, collaborative approach to engaging with clients from various business lines and agencies to capture, tabulate, and analyze the necessary data for submission. In order to meet the requirements of the IDC with accurate data, NISH team members work with the Office of the Chief Information Officer (OCIO) to effectively collaborate and engage with the agency’s various business lines. Through their participation in the cross-functional data validation process, key stakeholders sign-off on the accuracy of the submission.The sign-off allows each agency business line to explain how they reported a particular metric of the data collection, in the event of an audit by the Government Accountability Office (GAO).

NISH team members are well experienced and professionally driven to provide Federal agencies with the project management needed to execute a successful data collection process for the IDC. Prior to the submission due date, the NISH team members create and distribute a schedule of the data collection process to stakeholders. The schedule provides stakeholders with key milestones, submission throttle points, and an itinerary of weekly meetings. As the data is collected, we verify reporting metrics and validate the data requested to ensure it is accurate and relevant to the specifications set forth by OMB.

A challenge many agencies face is automating the IDC process into their day-to-day operations so that the quarterly reporting process is more streamlined and accurate. In some cases, this involves altering transaction codes to identify the specific metrics that are requested in the IDC. For example, one of the requested metrics in the IDC is an agency’s commodity IT spend. The commodity IT categories OMB defines consist of email systems, identity and access management systems, mainframes and servers, mobile devices, etc. Data such as this must be captured in a separate field of an agency’s financial information system, and each commodity IT expense, or line item, must identify the commodity IT category to which it belongs.

Since PortfolioStat is still a relatively new reporting exercise, many agencies do not have transaction codes implemented to capture the full spectrum of commodity IT categories. This means that they must manually analyze each of their line items at the end of the quarter, to determine how to categorize each commodity IT expense. This can be a very tedious and time-consuming process.

In order to automate the identification of commodity IT, the individuals tasked with data entry must be trained to identify the commodity IT category to which the transaction best fits. Since this data will be recorded at the time of entry, rather than at the end of the quarter, the line items will not need to be manually reviewed again at the end of the quarter. Automation techniques, such as this, will save agencies a great deal of time and increase the accuracy of the reported IDC metrics.

Once all of the data has been collected from the agency business lines, the NISH team performs a final analysis and presents a summary of the data and any points of concern to OCIO management. With the support and approval of OCIO management, the data is then submitted through the OMB MAX website.

Results and Client Response

Since the IDC is now required to be submitted quarterly, the strong project management methodologies employed by NISH team members have enabled a seamless and streamlined IDC submission process. The NISH team continues to support our clients by:

  • identifying more concrete points of contact,
  • setting stakeholder expectations at the beginning of the process,
  • providing a collaborative process for determining reporting metrics, and
  • clarifying communication channels.

We strive to provide the highest levels of service excellence, not only in the way NISH team members manage the IDC but also with the reliable and actionable data that the IDC provides.

Consulting service offering data to improve

Chief Information Officers (CIOs) must manage business and IT applications as assets. The applications must have a positive return on investment (ROI) in order to justify their existence. The business value for computing the ROI may consists of productivity, revenue, regulatory compliance, and mission criticality.

With increasing budget constraints and rapid technology innovation, IT leaders are under increasing pressure to manage their application portfolio efficiently while leveraging modern technologies. Outdated, obsolete, and redundant legacy applications stifle IT innovation. Business surveys show that legacy IT systems are not only inhibiting IT departments’ modernization efforts, but are also threatening to curtail business improvement and growth.

Application Rationalization is an analytical approach to decisions about maintaining, upgrading, modernizing, and retiring applications. Organizations can use it to free-up IT resources from unused, redundant, and “high maintenance” legacy applications and create an effective roadmap for each application and modernization project pipeline. Application Rationalization also prepares the application portfolio for valuable IT initiatives, such as digital signature, identity management, and cloud migration (Platform-as-a-service or Software-as-a-service).

NISH’s approach to Application Rationalization is pragmatic and based on industry best practices. Our approach includes the following recommended activities:

  1. Obtain executive and upper management sponsorship, especially from the  business.
  2. Establish and communicate goals with clearly defined milestones (aka project plan).
  3. Assemble a team of business and IT analysts, IT architects, cost analysts, and project manager.
  4. Adopt a methodology (including evaluation criteria) and transparent process.
  5. Identify and engage both business and IT stakeholders throughout the process.
  6. Use one tool to collect and analyze data.
  7. Communicate regularly and frequently.
Consulting service offering data to improve

The Federal Information Technology Acquisition Reform Act (FITARA) requires Federal agency heads to ensure that their respective chief information officers (CIOs) have a significant role in information technology (IT) decisions, including annual and multi-year planning, programming, Time for Changebudgeting, execution, reporting, management, governance, and oversight functions. The Office of Management and Budget’s (OMB) annual information technology capital planning guidance directs Federal CIOs (excluding the military departments) on how to implement the law.

The guidance outlines CIO responsibilities and authorities under FITARA and directs them to: (1) approve their agency’s IT budget requests, (2) certify that IT investments adequately implement incremental development, and (3) ensure that all requested IT positions meet ongoing requirements.

As OMB is finalizing the guidance on how to address the requirements of the new law, federal leaders can begin with these three steps:

  1. Establish an agency-level “FITARA board” – Senior leadership of the department/agency should immediately establish a “FITARA board,” responsible for addressing the FITARA requirements and reporting to both the department/agency head as well as oversight bodies such as OMB and Congress. Chaired by the CIO, the board membership should include the chief financial officer (CFO), chief acquisition officer (CAO), and chief management officer (CMO).
  1. Define scope of IT – The CIO should review the current scope of department/agency IT investments and application of IT spending under under OMB Circular A-11. FITARA defines a much broader scope for IT resources, in comparison to the Circular and the Clinger-Cohen Act. As a result of this expanded perspective, the CIO may be required to update the current definition and scope of IT resources in the  department/agency.
  1. Evaluate current governance processes – Current governance processes for IT budget, acquisition, and program management are likely “siloed” and fragmented in most agencies.

In depth-review of these processes, to identify the gaps in addressing FITARA requirements, will help the CIOs implement integrated governance processes that are based on the principles of transparency, risk management, and accountability.

These steps are initial recommendations for how agencies and departments can begin to address some of the FITARA requirements. In the days and months to come, a comprehensive implementation plan will be needed to effectively address FITARA and achieve the goals of improved management and oversight of IT resources.


OMB has published proposed guidance to implement FITARA and is seeking feedback from the general public. Vist https://whitehouse.github.io/fitara/.

Consulting service offering data to improve

The Federal Information Technology Acquisition Reform Act (FITARA) requires the heads of Federal agencies to ensure that their respective chief information officers (CIOs) have a significant role in information technology (IT) decisions, including annual and multi-year planning, programming, budgeting, execution, reporting, management, governance, and oversight functions. The law also requires the Office of Management and Budget (OMB) annual IT capital planning guidance to require CIOs to (1) approve their agency’s IT budget requests, (2) certify that IT investments adequately implement incremental development, and (3) ensure that all requested IT positions meet ongoing requirements. Click FITARA to review the law in its entirety. Also, visit https://whitehouse.github.io/fitara/ to provide feedback on OMB’s proposed guidance.