|
February 2007

AMM Team Deploying Phase One Modules on Schedule
The NASA Aircraft Management Module (AMM) Project Team is giving a pat on the back to the center support folks who were integral in deploying the Phase One modules for go-live at Marshall Space Flight Center January 10, 2007; at Wallops January 24, 2007; and at Kennedy Space Center February 8, 2007. Ames Research Center will be incorporated as a part of the Dryden Flight Research Center (DFRC) Phase One implementation during the week of February 21. (With the SOFIA aircraft transferred to DFRC, through Operational testing period, Ames is left without an aircraft to permanently possess).
The early deployments of the Phase One modules have flushed out some new and valid requirements for the AMM Project, including the ability to publish the flying schedule to an external web-server to a wider audience at the centers. The project team reports that some centers utilize simulators to satisfy more crew currency requirements than the project team had previously interpreted from center requirements. The team says they will wait until deployment is wrapped up before implementing any curative change requests.
The AMM Project will provide an integrated toolset for the management and oversight of NASA’s mission management aircraft, mission support aircraft, and research aircraft. The project, which initiated at Johnson Space Center, was added under the auspice of the Integrated Enterprise Management Program (IEMP) in 2005. The AMM system is intended to eliminate the risk of flying aircraft with overdue inspections, grounding discrepancies, with unqualified or non-current aircrew, or in aircraft not properly configured for the mission. AMM also expects to provide positive control and reporting of all aircraft-related assets and reduce the cost of operations. Likewise, the project is intended to give users timely and user-friendly access to the data and information they require to carry out their jobs.
This is the last year that NASA will have to struggle to manually file the annual Aircraft Utilization and Cost report with GSA. Once in operation for an entire year, NASA Aircraft Maintenance Information (NAMIS) should be able to provide all of the utilization data to HQ within an hour’s time.
Back to Top

eTravel awaits direction; doesn’t stall
The Integrated Enterprise Management Program’s eTravel team continues to wait out the results of a schedule re-baseline. Still, despite the lack of an updated, concrete schedule, the team has been inside these last few chilly, snow filled weeks working to ensure functional team members completed user acceptance testing (UAT) required for the latest release of FedTraveler.com.
The eTravel team also initiated Sprint 2 development activities that support integrations with NASA’s financial, human capital, account management and reporting systems. They also conducted the eTravel Monthly Risk Review meeting and completed the Performance and Architecture Test Plan document.
eTravel is one of the original 24 eGovernment initiatives outlined by President Bush in July of 2001. The effort was designed to make better use of information technology and to eliminate billions of dollars in federal spending, reduce paperwork and improve government response time to citizens. As a result, FedTraveler.com, an integrated application, will be implemented to give NASA online booking, travel authorization, and travel vouchering capabilities.
Looking ahead, the eTravel team continues to analyze potential options for NASA’s direction on the project’s release strategy. In the meantime, the team will work to make more headway developing a system interface between NASA and FedTraveler.com. Assessments of the Organizational Impact on policies, travel processes and roles and what they mean to training and change management activities still need to be completed. Operations and maintenance procedures for Web Based Training, training environment and the training manuals all need to be determined, defined, and drafted.
Back to Top

HCIE ready to roll with new i-View page
With the Human Capital Integrated Environment (HCIE) Project’s Steering Committee charter approved, and the team’s Exhibit 300 completed, HCIE, is moving fast towards a 2007 rollout. After a series of planning meetings, HCIE is ready to roll with the newly developed portal. The project team is continuing to determine exactly what content should be included on this portal page. The new portal will rollout to NASA’s Human Resource community on March 1st and to the entire NASA community in July.
HCIE is a partnership between the NASA Office of Human Capital Management (OHCM), Integrated Enterprise Management Program (IEMP), and the NASA Shared Services Center (NSSC). The project’s purpose is to deliver NASA human capital information, tools and services using a personnel data warehouse and a portal front end. The personnel data warehouse (PDW) will serve as the authoritative data source for NASA human capital information and users will access all human capital data through a single portal that provides the customer interface.
Back to Top

February focused on IAM change management
After kicking off 2007 with a long list of January achievements, the Integrated Enterprise Management Program’s Integrated Asset Management (IAM) Property, Plant and Equipment (PP&E) project didn’t back off from their “to do list” in February. The NASA IAM change management team has been focusing energy on unifying the IAM center teams. In an effort to really make the change management effort successful, IAM PP&E gathered the Center Implementation Project Managers (CIPM), along with members of the Center Change Management teams (CM) in late January at Johnson Space Center. The face-to-face meeting was scheduled to kick off preparations for delivering change management in anticipation of the project implementation.
The IAM Agency Process Team also reported logging “continued process analysis work” among their top accomplishments for the past month. The project is working towards implementation in the fall of 2007. But PP&E is also helping to break new ground within the IEM Program. The team is testing a new Agile “Scrum” software development methodology. As a result, the team is responsible for starting to develop iterative and incremental activities which are now underway.
IAM PP&E functionality will be implemented for NASA-owned/NASA-held, or NASA owned/contractor held assets to better control accountability, valuation and tracking of internal software, theme assets and personal property.
The Department of Energy’s (DOE) Oak Ridge National Laboratory version of SAP PP&E will serve as a model for process and configuration at NASA. The DOE system uses standardized SAP functionality for creating asset records within SAP Asset Accounting module. These components are part of either SAP R/3 or the SAP web application. Custom transactions within SAP R/3 are provided for the property management team to perform their functions. The web-based interface is provided for the general user community to manage property. NASA will use SAP to manage all capital assets and all those controlled assets that qualify for management currently under the NASA Equipment Management System (NEMS) and the NASA Property Disposal Management System (NPDMS).
Back to Top
|