Attachment A - IDIQ PWS Final.pdf

NATIONAL SCIENCE FOUNDATION

Attachment A:

Financial System

Implementation, Hosting, and Business Transaction Services

Table of Contents

1.0 Introduction

2.0 Background

3.0 Current Environment

3.1 Limitations of As-Is Environment

4.0 Objectives and Goals

5.0 General Requirements

6.0 Scope of Work

6.1. Implementation Services

6.2 Integration to NSF Systems

6.3 Integration to Federal Systems

6.4 Hosting Services during implementation and integration

6.5 Software Licenses

6.6 Project Management

6.7 Organizational Change Management & Training

6.8 Hosting, Operations and Maintenance Services

6.9 Transition Services (Optional Task)

6.10 Enhancement Services (Optional Task)

6.11 Business Process Support (Optional Task)

7.0 General Information

7.1. Data

7.2 Key Personnel

1.0 Introduction

The purpose of this Performance Work Statement (PWS) is to obtain services to support the

National Science Foundation (NSF) in implementing a commercial off-the-shelf (COTS) Core

Financial management system and interfaces in a hosted environment. NSF seeks to establish a contract that will provide a range of support for implementing and maintaining the financial management system under an initiative called iTRAK. This initiative will be conducted in compliance with all applicable Federal financial systems regulations and guidance. Specifically:

Chief Financial Officer’s Act of 1990

Clinger-Cohen Act (also known as the Information Technology Management Reform

Act)

FASAB SFFAS #6, A-136

Federal Manager’s Financial Integrity Act of 1982 (FMFIA)

Federal Financial Management Improvement Act of 1996 (FFMIA)

Federal Information Security Management Act of 2002

Federal Acquisition Regulation, March 2005 Edition

Financial Systems Integration Office (FSIO) core financial systems requirements;

Governmentwide Accounting (GWA)

Federal Accounting Standards Advisory Board Standards (FASAB)

Federal Information Security Management Act of 2002

Freedom of Information Act amendments 5 USC 552 and 5 USC 552a

Generally Accepted Accounting Principles

Government Information Security Reform Act (Title X, Subtitle G of the Defense

Authorization Act)

Government Paperwork Elimination Act

Government Performance and Results Act

Government Management Reform Act

Internal Revenue Code 6103 security constraints

IRS Publication 1075 security constraints

National Institute of Standards and technology (NIST) Special Publications (800 series)

Federal Information Processing Standards (FIPS) 199

NIST Special Publication 800-53, Recommended Security Controls for Federal

Information Systems

OMB Circulars A-11, A-123, A-127, A-130, and A-134.

OMB Guidance on Financial Systems Efforts

OMB Memorandum M-10-26, Immediate Review of Financial Systems IT Projects

OMB Memo 05-02, Financial Management Systems

"OMB Competition Framework for Financial Management Line of Business Migrations,"

Financial Management Line of Business Migration Planning Guidance

Paperwork Reduction Act

Presidential Decision Directive PDD-63

Section 508 of the Rehabilitation Act

Tax Increase Prevention and Reconciliation Act of 2005

Treasury’s USSGL iTRAK is a joint effort between the Office of Budget, Finance and Administration (BFA) and the

Office of Information Resources Management (OIRM). The BFA includes the Chief Financial

Officer’s office and the OIRM includes the Chief Information Officer’s office.

2.0 Background

The NSF mission is "To promote the progress of science; to advance the national health, prosperity, and welfare; to secure the national defense." To fulfill this mission, NSF has an annual budget of over $6 billion and is the premier Federal agency supporting research across all fields of nonmedical science and engineering education. NSF funds more than 40 percent of the

Federal support for nonmedical basic research at America's colleges and universities, and in

2008 alone, provided funding to 1,900 colleges, universities, and other institutions. With the creation of the American Recovery and Reinvestment Act (ARRA) in 2009, NSF's budget increased to $9 billion. In addition, since 1952, the Foundation has supported approximately

44,000 students through Graduate Research Fellowships and annually provides direct support to researchers, postdoctoral fellows, trainees, and teachers as well as students. Through its investment in people—their education and the research they conduct—NSF helps keep America at the leading edge of science, engineering, and technology.

3.0 Current Environment

Underlying the Foundation's investment in people are the financial management system and programs that enable funding for education and research initiatives to be received, allocated, and managed within budget and according to Federal laws and regulations. NSF's legacy financial management system, the Financial Accounting System (FAS), is the Division of Financial

Management’s (DFM) primary vehicle for managing funding allocated to the National Science

Foundation. Central transaction management represents the core of the system, handling transaction processing, accounts maintenance, transaction history, and rules processing. The system includes extensive reporting capabilities to assist DFM and Administrative Officers in verifying funds throughout the fiscal year. The system support extensive editing for transactions input through the FAS as well as from other systems that interface with the FAS system. This system went into production in the client-server environment on April 23, 2001.

Technical Description: The FAS was written and currently maintained using the following environments:

Application Software: C++, Sybase PowerBuilder V10.x with

NSF PFC Framework

Database Engine: Sybase SQL Server System 12.5.0.3

Database Server: Sun E5500 Unix Server Running Solaris (Development)

SunFire 6800 Unix Server/Solaris (Production)

SunFire 6800 Unix Server/Solaris (User Acceptance)

Unix Operating System: SunOS 5.8

Communication: Sybase Open Connect

Client Workstations: Windows 9X, Windows NT, Windows XP

Version Control: Rational ClearCase (UCM enabled)

Special Features: Multiple-Document-Interface (MDI) Application, GUI Front-End, TDClient Version V2.0

Word Processing: MS WORD, MS-RTF

Reporting: Custom Built Batch Infrastructure for Accounting System, MS

Access 2000 and Excel for AD-HOC Reporting.

Batch Job Scheduling: BMC Control/M for client server

IMB Rational Tools: ClearQuest, Test Manager, Robot

3.1 Limitations of As-Is Environment

FAS requires increasing time, effort, and funding to operate, maintain, and remain in compliance with Federal financial management regulations. While FAS has served the Foundation well for more than 20 years, the antiquated technology on which FAS is built makes continued compliance with Federal financial management requirements increasingly difficult and costly. It also severely limits NSF's ability to respond to emerging internal business needs and goals.

More specifically, FAS poses the following performance gaps:

Inadequate automated processing support and controls. The system has many manual processes, with a high potential for human error and duplication of effort. These manual processes increase both the level of effort to develop and test system change requests and the risk of reduced financial information integrity, effectiveness, and timeliness. This was an audit finding during the 2008 and 2009 financial statement audits.

Lack of standard business processes and key functionality. As an in-house, legacy financial system, FAS has evolved based on immediate needs rather than strategic goals over the past two decades. FAS is expensive to operate and maintain, relies on outdated architecture and technologies, and offers very limited management and decision support functionality— it does not meet NSF's mission requirements.

Transparency. The Federal Funding Accountability and Transparency Act of 2006

(FFATA) established new award reporting requirements and procedures in an effort to increase the transparency of federally funded awards. In addition, the American Recovery and Reinvestment Act of 2009 (ARRA) also created new, separate reporting requirements necessitating increased transparency, accuracy, and frequency of financial data. To meet

FFATA and ARRA requirements, FAS requires difficult and costly modifications, which can be better met by a COTS financial shared services solution.

Non-Compliance Risk. The system is at risk of not meeting Federal standards, such as

OMB Circular A-127, FFMIA, FMFIA, and Treasury mandates.

OMB Circular A-127. A-127 requires agencies to record financial events at the transaction level consistent with applicable definitions, attributes, and processing rules of the USSGL. FAS has a number of transaction codes non-compliant with the U.S. Standard General Ledger (USSGL) and established Treasury standards.

Federal Core Financial System Requirements. A growing number of variances exist between current FAS functionality and Federal Core Financial systems requirements. Examples include the following:

FAS lacks the capability to produce Financial Statements. As a result, NSF must maintain statements in Excel spreadsheets, which requires extensive manual operations and data manipulation.

FAS does not have the functionality to track the details of receivables.

This information is stored and tracked in Excel spreadsheets, increasing the risk of miscalculations or human errors due to lack of automation and adequate controls.

Costly Maintenance. FAS is at the end of its lifecycle, with a greater share of its maintenance budget spent on fixes rather than value-added enhancements. (In FY 2007, 95% of the FAS budget was spent on daily operations and preventive activities with only

5% of the budget focused on closing compliance gaps.)

4.0 Objectives and Goals

The objectives of the iTRAK solution are to provide robust functionality and financial information that will facilitate management decision making and create operating efficiencies in supporting NSF’s mission. iTRAK will position NSF to provide accurate and reliable financial information to the Science Directorates and the grantee community without the substantial manual processes; address growing financial reporting requirements; maintain clean audit opinions; and provide continued financial management excellence to NSF.

The objective of iTRAK is the successful implementation of a COTS Core Financial management system and key interfaces. Specific iTRAK goals are as follows:

Goal I. Increase capabilities for more informed operational and programmatic decision-making.

1. Improve financial data accuracy and consistency.

2. Improve enterprise-level financial data access, transparency, and reporting.

3. Make timely and accurate financial data available for NSF Program Managers to track and monitor program progress.

Goal II. Improve effectiveness and efficiency of financial and business processes.

1. Implement standard business processes and operating procedures.

2. Reduce manual processes.

3. Integrate data to reduce redundancy and reconciliation issues.

Goal III. Enhance financial and business accountability, integrity, and compliance.

1. Automate controls and reconciliation points where appropriate

2. Improve traceability of transactions where appropriate

3. Provide for system flexibility and agility to meet current and future mandated

Federal requirements.

5.0 General Requirements

iTRAK scope includes implementing a COTS Core Financial management system and key interfaces, hosted in a shared service environment. At a minimum, the items listed below shall be supplied and performed in accordance with the terms and conditions of the contract.The solution selected by NSF shall be able to demonstrate the following capabilities:

Utilize a Core Financial management system that is compliant with Federal Financial

System requirements;

Comply with any additional applicable requirements, such as privacy, security, compliance with section 508 of the Rehabilitation Act, continuity of operations, critical infrastructure protection, disaster recovery, service level agreements, and help desk services;

Comply with standards mandated by OMB and Treasury;

Integrate with Standard Federal Interfaces (FedTraveler, Central Contractor Registration

(CCR), Federal Procurement Data System - Next Generation (FPDS-NG);

Comply with Shared Services Requirements - NSF desires to have the system hosted by a provider with operations and maintenance provided;

Integrate to third-party software and NSF Mission Systems;

Comply with NSF-specific requirements for the COTS shared services solution;

Comply with NSF system and security requirements.

NSF does not intend to customize the COTS financial management solution and instead will adopt business processes to realize the full benefits of the best practices and efficiencies built into the COTS software. NSF unique requirements will be addressed with configuration and not customization. Specific requirements are detailed in Attachment B: iTRAK Business

Requirements and Attachment C: Interface Requirements.

6.0 Scope of Work

The Contractor shall implement a commercial off-the-shelf (COTS) Core Financial management system and key interfaces in a hosted environment. The items listed below shall be supplied and performed in accordance with the terms and conditions of the contract. The Contractor shall furnish the following:

1. Implementation services

2. Integration with NSF Systems

3. Integration with Federal Systems

4. Hosting services during integration and deployment

5. Project Management

6. Organizational Change Management & Training

7. Software Licenses (COTS Core Financial Management solution)

8. Transition Services

9. Hosting, Operations, and Maintenance

10. Business Process Support Services

11. Enhancement Services

The iTRAK project timeline calls for the implementation effort to begin April 1, 2012 and for the new financial system to achieve full operational capability in a hosted environment by

October 1, 2013. NSF prefers to go-live at the beginning of the fiscal year. Full operational capability is defined as the iTRAK Core Financial system becoming NSF’s financial system of record, with all Federal Financial System requirements and NSF specific requirements; all batch and online financial transactions, executed at the hosted location; including all NSF and Federal interface functionality. All reports shall be configured, working and accessible by users on

October 1, 2013.

6.1. Implementation Services

The Contractor’s proposed implementation approach and schedule shall demonstrate the interdependencies of all activities. The Contractor shall provide all necessary services for the successful implementation a COTS Core Financial management system that is compliant with

Federal Financial System requirements and OMB Memo 10-26. The following implementation services objectives have been identified:

System Configuration

Data Migration and Conversion

System Testing

Develop Accounting Code Structure

System Documentation

Financial Reports

System Deployment, Cutover and Release Management

6.2 Integration to NSF Systems

The Contractor shall provide all necessary services for the successful integration of the COTS

Core Financial management system with NSF systems.

6.3 Integration to Federal Systems

The Contractor shall provide all necessary services for the successful integration the COTS Core

Financial management system with Federal systems.

6.4 Hosting Services during implementation and integration

The Contractor shall provide hosting services during integration and deployment to support solution development, configuration, integration, data migration, testing, and staging. The hosting solution shall be in compliance with OMB guidelines and includes all services necessary to deliver the proposed approach from project initiation through system cut-over. The following hosting services objectives have been identified:

Hardware and software

Implementation environments (development, testing, training)

6.5 Software Licenses

The Contractor shall provide an enterprise COTS license solution, all warranties, terms and conditions. The estimated number of NSF users is 561. The Contractor shall include the methodology and pricing for adding licenses in the future if needed.

6.6 Project Management

The Contractor shall provide comprehensive and effective life cycle project management services and shall employ a management approach that is consistent with NSF's system development methodology, the Continuous Improvement Program (CIP) and project management best practices, notably those specified by the Project Management Institute (PMI).

Details on CIP can be found in Attachment D: Division of Information Systems (DIS) Systems

Development Lifecycle. The Contractor shall provide detailed information on the project management structure, resources and support methodology. The Contractor’s project management support services, tools and processes shall include, but are not limited to:

Schedule Management

Scope Management

Risk Management

Project Financial Management

Document Management

Requirements Management

Configuration Management

Software Change Management

Quality Control

Cutover Management

CIP Documentation Support

Status Reporting

6.7 Organizational Change Management & Training

Organizational change management is a critical function in ensuring the acceptance and adoption of the new iTRAK financial system by NSF stakeholders. NSF requires transformation that aligns the business processes with the COTS solution. The Contractor shall be an active participant in the identification of transformational and organizational change issues (e.g., stakeholder transition, communications, and training) and in developing strategies for mitigating the impact and facilitating the adoption of new and reengineered business processes and supporting services.

The Contractor’s organizational change services, tools and processes shall include, but are not limited to:

Communications

Organizational change

Training

6.8 Hosting, Operations and Maintenance Services

Provide operations, maintenance and hosting services in a shared service environment. The items listed below shall be supplied and performed in accordance with the terms and conditions of the contract. The Contractor shall furnish the following:

Hosting Services

Operations and Maintenance Services

The Contractor shall perform all hosting, operations and maintenance (O&M) activities for the new financial system including the security of the deployed system infrastructure. The

Contractor shall be responsible staying up-to-date with current software versions. The Contractor shall be responsible for providing a change control process that enforces consistent configuration management across all increments, instances, and upgrades of the new financial system.

The iTRAK project timeline calls for the new financial system to achieve full operational capability in a hosted environment by October 1, 2013. The Contractor shall perform all hosting, operations and maintenance (O&M) activities for the new financial system including the security of the deployed system infrastructure. The Contractor shall be responsible for providing a change control process that enforces consistent configuration management across all increments, instances, and upgrades of the new financial system.

6.8.1 Hosting Services for Production

Hosting Services involves providing the information technology (IT) infrastructure (facilities, infrastructure, hardware, and software) that serve as the foundation for running business software applications and the services to maintain that infrastructure. The Contractor shall provide all the necessary services to host the solution, consistent with the goals and objectives of this PWS.

Hosting support includes but is not limited to the maintenance and operation of the hardware, data center support, software and telecommunications in support to the application.

The following hosting objectives have been established:

The Contractor shall provide all hardware, software, and infrastructure needed to host the proposed COTS solution.

The Contractor shall provide a complete hosting solution in compliance with OMB

Memo M-10-26, OMB Circular A-127, SSAE 16 requirements, all Federal Financial

System and Security requirements, and NSF requirements and includes all services necessary to deliver the proposed approach for system cut-over and all post-deployment production operations.

The Contractor shall provide the activities associated with transitioning into the production environment hosted by the SSP including facilities, hardware, software, data, and support transition.

The Contractor shall provide hosting support includes but is not limited to maintenance and operation of the hardware, data center support and internet connection in support of the application.

The Contractor shall ensure that a proper Continuity of Operations plan (COOP) and

Disaster Recovery is in place.

The Contractor shall establish and maintain application security and access controls.

The Contractors shall prepare and execute Service Level Agreement (SLA) that includes the performance indicators. Detailed technical and service level agreement requirements and metrics are in Attachment C: Interface Requirements, Attachment E: Service Level

Agreement Technical Requirements and Attachment F: Hosting, Operations, and

Maintenance Performance Metrics.

6.8.2 Operations and Maintenance Services

Operations and Maintenance Services involve providing the software and the services for running and managing the financial management software. The Core Financial solution shall consist of the use of Commercial-Off-The-Shelf (COTS) products with limited product extensions and limited customization of the core product. The Contractor shall be required to integrate operational components and configure the integrated solution to operate within the hosted environment. The foundation of the proposed solution must be compliant with Federal

Financial System requirements. Application Management/Operations and Maintenance support includes but is not limited to functional and technical tasks directly related to the application which includes issue resolution, offline processing, any reference table updates, report maintenance in the software, monthly, quarterly and annual close processing, database dumps, and implementation and testing of new regulatory requirements. Software license maintenance costs and system upgrades are considered a part of hosting services.

The following application management/operations and maintenance objectives have been established:

The Contractor shall perform all operations and maintenance (O&M) activities for the new financial system including all application functional and technical support and security of the deployed solution including.

The Contractor shall provide a process for software patching (changes to the software that are fixes and changes in a future software release that is needed prior to implementing the new release) and when major and minor software releases will be installed and the process for communicating the changes to the end users.

The Contractor shall provide a change control process that includes customer input and enforces consistent configuration management across all increments, instances, and upgrades of the new financial system.

The Contractor shall provide Tier 1, 2 and 3 help desk support.

The Contractor shall prepare and execute Service Level Agreement (SLA) that includes the performance indicators outlined in the SLA requirements in Attachment E: Service

Level Agreement Technical Requirements and Attachment F: Hosting, Operations, and

Maintenance Performance Metrics.

6.9 Transition Services (Optional Task)

Transition services under this contract are critical to the Government and must continue without interruption. When the contract expires, a successor, either the Government or another contractor, may continue the services. The Contractor shall, apply its best efforts and cooperation to carry out an orderly and efficient transition to a successor. The contractor shall develop, document, and execute a transition plan that may be used to transition tasks and materials to a new SSP contractor or to the Government. The transition plan shall incorporate an inventory of all deliverables under this contract. The plan shall include a schedule of briefings, including dates and time and resources allotted, that will be required to conduct a full transition. The plan is to ensure that the Government will be provided all of these deliverables and be fully briefed at least 90 days prior to the expiration date of the current task order or contract. Specific requirements will be addressed in a Task Order.

6.10 Enhancement Services (Optional Task)

After iTRAK implementation, NSF may decide to develop enhancements to the system based on user requests and business needs. This task is not for enhancements that are part of regular software maintenance that shall be included in 6.2 Hosting, Operations, and Maintenance

Services. Application enhancements may be requested in response to changes in NSF business requirements. Enhancements might originate with user requests for specific capabilities or from management identification of solutions to substantive routine system problems. The Contractor shall document any enhancements following the agreed upon change control process, and follow the change control process to receive approval for the enhancement. The Contractor shall assist in designing, developing and implementing enhancements. Specific requirements will be addressed in a Task Order.

6.11 Business Process Support (Optional Task)

NSF is currently considering outsourcing transaction processing. The transactions that are currently under consideration are:

Commercial payables/disbursements/reconciliation

Travel payables/disbursements/reconciliation

Draft Financial Statements (Quarterly and Yearly)

Detailed transaction volume data is available in Attachment G: NSF Transactional Volume Data.

Specific requirements will be addressed in a Task Order.

7.0 General Information

Performance based Task Orders will be issued against this contract as requirements are defined.

Task Order procedures will be established in the IDIQ under the General Terms and Conditions section.

7.1. Data

NSF will own transactional data, static data and NSF generated data

NSF will receive functional and technical design specifications and all updates

NSF will receive documentation of configuration and all updates

7.2 Key Personnel

The tables below contain a list of the key personnel and a description of the relevant experience.

The Contractor may propose additional key personnel and non key personnel positions based on its past experience in the organization and execution of projects that are similar in size, scope and complexity. In such event, the Contractor shall include the rationale for this staffing approach in the Staffing Plan.

The IT Project Manager, Senior Business Analyst, and Senior Integration Analyst must have previous experience implementing the proposed Core Financial management system for a

Federal government agency or component subject to the Chief Financial Officers Act or

Accountability of Tax Dollars Act.

Key Personnel NSF

Labor Category Position Description and Level of Experience

IT Project Manager B.S. or B.A. degree or equivalent experience; additional professional certifications preferred; Must have 13 years of IT experience, including at least 8 years of IT system management experience.

Specialized Experience: At least 8 years of direct supervision of IT software development, integration, and maintenance projects. Must be capable of leading projects that involve the successful management of teams composed of data processing and other information management professionals who have been involved in analysis, design, integration, testing, documenting, converting, extending, and implementing automated information systems.

Project Control Specialist

- EVM

B.S. or B.A. degree or equivalent experience with EVM experience preferred; Monitors financial and/or administrative aspects of assigned contracts and deliverables. Tracks and validates all client financial information, establishes and maintains master contract files, prepares and monitors status of all deliverables, tracks the value of contracts, and reports payment of government fees. Updates task reports with funding information and prepares revenue projections for all active contract task orders. Uses automated systems to track deliverables, financial transactions, and management information

Project Control Specialist

- Risk Manager

B.S. or B.A. degree or equivalent experience with Risk Management experience preferred; Monitors financial and/or administrative aspects of assigned contracts and deliverables. Tracks and validates all client financial information, establishes and maintains master contract files, prepares and monitors status of all deliverables, tracks the value of contracts, and reports payment of government fees.

Updates task reports with funding information and prepares revenue projections for all active contract task orders. Uses automated systems to track deliverables, financial transactions, and management information

Senior Business Analyst -

Functional Lead

B.S. or B.A. degree or equivalent experience; additional professional certificates preferred; Must have 10 years of financial management experience; Serves as a group leader ensuring that a group of analysts are working in concert to automate complex business practices within the time frame specified by the customer and that all of the requirements are met. Must be able to assess products and procedures for compliance with government standards, accounting principles, and multi-tiered system application standards. Must be able to grasp interrelationships between financial management requirements and automation solutions, considering the current system environment and the potential integration of added systems concurrently or later. Prepares milestone status reports and presentations for colleagues, subordinates, and end user representatives. Coordinates all aspects of complex financial application automation, requesting guidance only in extremely difficult situations. Completes objectives independently within the negotiated budget.

Senior Integration

Analyst - Technical Lead

B.A. or B.S. degree or equivalent experience; Must have 10 years of working experience as a computer systems analyst; Must be knowledgeable in implementing computer systems in a phased approach of requirements analysis and conceptual design, site survey, system design review, critical design review, installation, integration, and testing. Must be knowledgeable in performing requirements analysis for a wide range of users in areas of office automation and finance and accounting. Must be able to present system designs for user approval at formal reviews. Must be capable of performing configuration management, integrating software, interpreting software test results, and recommending solutions for unsatisfactory test results. Must be knowledgeable in lifecycle support, including maintenance, administration, and management.

Must be able to provide solutions to identified software problem reports.

Senior Integration

Analyst - Data

Conversion Lead

B.A. or B.S. degree or equivalent experience in a related field.

Performs as an experienced professional in the complex technical area of data conversion. Provides specific technical area analysis and recommendations reflecting detailed, expert knowledge of a specific subject area or technology. Develops benchmarks. Performs elaborate analyses and studies. Develops reports and makes presentations to contractor management and senior client executives.

Senior Integration

Analyst - Testing Lead

B.A. of B. S. degree or equivalent experience; This position is needed as the Testing Lead: Develops, plans, organizes, and leads major segments of and/or entire consulting projects. Determines technical objectives, defines data requirements and methodology, and recommends staffing levels and schedules. Reviews and coordinates the progress of other team members, taking corrective action as appropriate. Responsible for all and/or major segments of multiple project output and deliverables.

Senior Business Analyst

(BPR) Specialist -

B.A. or B.S. degree or equivalent experience. Will have 7-10 years of experience with change management, communications, business

Business Transformation

Lead process redesign, organizational development, training, project management, and process improvement. Experience developing and executing training for new system implementations to include role mapping, organizational readiness, and alignment activities.

Experience leading change and communication activities for systems implementations leading a team and integrating change tasks across systems implementations. Demonstrated ability to communicate with senior executives. Experience managing the implementation of change management projects including stakeholder engagement, leadership alignment, organizational development, knowledge management, and culture and communication issues.

Senior Training

Specialist - Training Lead

B.A. of B. S. degree or equivalent experience; Designs, develops, documents, and delivers training courses to a wide range of audiences. Employs various training techniques including formal lectures, tutorials and self paced exercise, and computer-based training. Provides professional guidance to Contractor management, analysts, specialists, programmers, and Government personnel in the use of the software.