AccessibilitySkip to Top NavigationSkip to Main ContentHome  |  Contact IRS  |  About IRS  |  Site Map  |  Español  |  Help  

Part 1. Organization, Finance and Management

Chapter 1. Organization and Staffing

Section 12. Chief Information Officer (Cont. 1)

1.1.12  Chief Information Officer (Cont. 1)

1.1.12.7 
Associate Chief Information Officer for Applications Development

1.1.12.7.5 
Corporate Data Domain

1.1.12.7.5.10 
Customer Account Data Engine (CADE) Branch

1.1.12.7.5.10.1  (04-01-2007)
Delivery Assurance Office

  1. The mission of the Delivery Assurance Office is to ensure the development, implementation, and monitoring of cross-release activities for the CADE program. The organization’s major responsibilities can be grouped into two distinct categories: program and transition management, and strategic planning and budgeting.

  2. To accomplish its mission, the Delivery Assurance Office will:

    1. Coordinate acquisition planning, acquisition management, and task order development and issuance.

    2. Oversee the Acquisition Management Plan (IRS and PRIME).

    3. Manage budget formulation and execution (PRIME Project and Internal BSMO Budget).

    4. Manage Independent Government Cost Estimates for Acquisitions.

    5. Manage proposal development, issuance, and review.

    6. Manage Independent Third Party Assessments (SEI).

    7. Oversee Risk and Issue Management Coordination, Configuration Management Coordination (CADE PrCCB, and Change Requests, MITS CCB).

    8. Coordinate all activities with external oversight organizations (OMB, GAO, TIGTA, etc.).

    9. Maintain contents of DMS.

1.1.12.7.5.10.2  (04-01-2007)
Operations and Maintenance Office

  1. The mission of the Operations and Maintenance Office is to provide taxpayers and other external and internal customers with a world-class CADE production system by ensuring efficient, effective, and successful deployments, operations, and maintenance of CADE production releases.

  2. To accomplish its mission, the Operations and Maintenance Office will:

    1. Oversee CADE development and testing activities (FIT and GAT) to ensure systems are deployment ready.

    2. Coordinate on-going infrastructure-related dialogue with Enterprise Operations and IRS stakeholder organizations.

    3. Monitor CADE performance engineering, and ensure that CADE design and deployment meet efficiency requirements.

    4. Maintain production support and production environments, and coordinate deployment activities.

    5. Maintain CADE production baseline and monitor day-to-day production activities, risks, and issues.

    6. Monitor CADE quarterly maintenance build and implementation status on fixing defects.

    7. Coordinate and develop End-of-Year and Mid-Year activities.

    8. Support IRS annual Disaster Recovery practices.

    9. Support stakeholder organizations on transition to support activities.

    10. Manage Operations and Maintenance Task Order and monitor contract performance on budget, schedule, and service level agreements.

1.1.12.7.5.10.3  (04-01-2007)
Requirements Management and Architecture Office

  1. The mission of the Requirements Management and Architecture Office is to ensure that both business and systems requirements are defined, formalized, and controlled. Specifically, focus will be placed on requirements management, business rules harvesting, Logical Modeling, and the packaging of requirements into allocated baselines for the various releases.

  2. To accomplish its mission, the Requirements Management and Architecture Office will:

    1. Establish and maintain project and client alignment.

    2. Maintain the CADE Release Content Master Plan.

    3. Serve as liaison with the Enterprise Services Requirements Management Office.

    4. Coordinate incoming and outgoing UWRs that impact CADE.

    5. Participate in the Modernization Vision and Strategy to ensure alignment of CADE and Account Management Services projects.

    6. Develop an interim repository of CADE requirements to ensure traceability to releases until an enterprise-wide repository is available.

    7. Support individual CADE releases to ensure that requirements allocated to a specific release are accurately reflected throughout task order development.

    8. Track the development of requirements throughout the acquisition and development process.

1.1.12.7.5.10.4  (04-01-2007)
Development Management Office

  1. The mission of the Development Management Office is to manage software development, testing, and deployment of releases on a planned cycle of twice per year. This typically would involve major functionality changes deployed by July 30th of each year and tax law changes deployed by December 31st of each year. The assigned functionality for the releases is provided by the Requirements Management and Architecture Office after approval by the business owner and operational support organizations. After each deployment, the office transitions the deployed code and documentation to the Operations and Maintenance Office for ongoing oversight and support.

  2. To accomplish its mission, the Development Management Office will:

    1. Manage the Milestone (MS) 3, 4A, and 4B work associated with each release.

    2. Develop all MS Exit materials and documentation.

    3. Manage the reviews and approvals for MS Exits for the ELC phases listed above.

    4. Manage the development budget to include execution against task orders, in effect providing input for future year requests, and validating cost, schedule, and performance data for inclusion in the E300.

    5. Manage the risks and issues identified relative to releases that impact development, testing, and deployment as well as cost and schedule for a release.

    6. Drive the active management of Change Requests related to releases through the PrCCB in conjunction with the Delivery Assurance.

    7. Monitor and evaluate vendor performance against task orders.

    8. Monitor and evaluate Earned Value reports and projections provided by the vendor.

    9. Conduct task order acquisitions for each assigned release.

    10. Ensure that an Independent Government Cost Estimate (IGCE) is developed for each task order acquisition.

    11. Ensure that the Product Assurance testing (GAT and FIT, where appropriate) activities are carried out for each release.

    12. Ensure that Quality Management practices are followed in each development task order.

    13. Ensure that Security and Privacy Certifications are obtained for each release.

    14. Deploy production-ready software to Enterprise Operations at the conclusion of MS 4B performance.

1.1.12.7.6  (04-01-2007)
Submission Processing Domain

  1. The mission of the Submission Processing Domain is to define, develop, design, build, test, deliver, and maintain integrated information application systems and to provide project planning and management for new business systems that focus on electronic or paper processing of tax return data and modernization initiatives.

  2. Submission Process has six subordinate offices:

    • E-File Development and Deployment Branch

    • Document Perfection Branch

    • Document Input Branch

    • Electronic Tax Forms Branch

    • Electronic Input Systems Branch

    • Excise Tax E-File and Compliance Systems Branch

1.1.12.7.6.1  (04-01-2007)
E-File Development and Deployment Branch

  1. The E-File Development and Deployment Branch has project management responsibilities for the Operations and Maintenance (O&M) transition activities and Modernized E-File (MeF) Releases 3.2, 4, and 5.

  2. To accomplish its mission, the branch will:

    1. Support development of the O&M production environment.

    2. Plan, direct, and coordinate development interfaces.

    3. Analyze and coordinate UWR requirements.

    4. Ensure quality systems testing and coordinate quality reviews with AD stakeholders and the Product Assurance organization.

  3. The branch has three subordinate offices:

    • O&M Section

    • MeF Release Team A

    • MeF Release Team B

1.1.12.7.6.2  (04-01-2007)
Document Perfection Branch

  1. The mission of the Document Perfection Branch is to plan, design, program, implement, maintain, and enhance computer systems which support pipeline processing systems that transcribe, validate, correct, and control income tax data.

  2. To accomplish its mission, the Document Perfection Branch will:

    1. Support imaging and data capture of electronic storage functions to process paper input documents.

    2. Support documents received through electronic data interchange.

    3. Support the programming and maintenance of the Batch Block Tracking System.

  3. The branch has four subordinate offices:

    • BMF Document Specific Section

    • IMF Document Specific Section

    • GMF/GUF/SCCF Section

    • ERS Section

1.1.12.7.6.3  (04-01-2007)
Document Input Branch

  1. The mission of the Document Input Branch is to provide project management of systems that process returns via manual input, imaging, and data capture; to deploy programs for Pensions and Remittances Processing; and to assist in the planning, coordination, requirements definition, interface definition, and development of systems to support Pensions and Remittances, ISRP, and SCRIPS.

  2. The branch has three subordinate offices:

    • Pensions and Remittances Section

    • Integrated Submission and Remittance Processing Section

    • Service Center Recognition Image Processing System Section

1.1.12.7.6.4  (04-01-2007)
Electronic Tax Forms Branch

  1. The mission of the Electronic Tax Forms Branch is to plan, design, develop, implement, and maintain computer applications for specific electronic initiatives.

  2. To accomplish its mission, the Electronic Processing Branch will:

    1. Support current Electronic Filing Systems (EFS) production.

    2. Plan, direct, and coordinate EFS program development interfaces to accept and process electronically transmitted data between IRS and external customers.

  3. The branch has four subordinate offices:

    • BMF/ELF Section

    • DCM/PAC Section

    • IMF/ELF Section

    • IMF/ELF Support Section

1.1.12.7.6.5  (04-01-2007)
Electronic Input Systems Branch

  1. The Electronic Input Systems Branch has program responsibilities for directing the planning, design, development, integration, and implementation of electronic modernization initiatives, and for supporting existing Electronic Tax Administration systems.

  2. To accomplish its mission, the Electronic Input Systems Branch will:

    1. Ensure products and services developed are monitored from original concept through operation using a well-defined set of controls, procedures, reviews, and standards to ensure high quality.

    2. Deliver systems timely, within cost and meet the needs of the customer.

  3. The branch has four subordinate offices:

    • Electronic Development Section

    • Electronic Federal Tax Payment System

    • CTW Section

    • Electronic Management System Section

1.1.12.7.6.6  (04-01-2007)
Excise Tax E-File and Compliance Systems Branch

  1. The mission of the branch is to deliver Excise Tax e-file and Compliance Systems (ETECS) products and services mandated by the American Jobs Creation Act and the Safe, Accountable, Flexible, Efficient Transportation Equity Act of 2005.

  2. To accomplish its mission, the branch will develop programs and systems to detect and prevent excise tax fraud.

  3. The branch has two subordinate offices:

    • Forms 2290, 720 and 8849 Section

    • ExFIRS and Compliance Systems Section

1.1.12.7.7  (04-01-2007)
Program Administration, Support and Services

  1. The mission of the Program Administration, Support and Services (PASS) is to provide administrative, logistical, analytical, and consultative support and services to the AD to assist in meeting leadership commitments and goals. The members of PASS work as a team to plan, coordinate, and support the AD program-level management and employee engagement meetings; develop and coordinate presentations, issue papers and reports to assist in meeting stakeholder and oversight requests; coordinate and prepare responses to AD audits, information requests, and data calls; and provide guidance, coordination, monitoring, and implementation of ISY budget and human resource and training activities.

  2. To accomplish its mission, the PASS office will:

    1. Coordinate formulation and execution of the AD Strategic Plan/Business Plan, bimonthly Ops Reviews/BPRs, ISY Budget, HPI process, and corrective actions to satisfy Material Weaknesses.

    2. Coordinate and provide administrative and analytical support for weekly ACID direct reports meetings, AD bi-monthly program reviews, bi-weekly MET meetings, bi-weekly MeF Mandate Advisory Committee meetings, quarterly All-Hands meetings, weekly brown-bag lunches, and other ad hoc meetings.

    3. Develop presentations, issue papers, and reports on program-wide and project-specific subjects and answer Congressional QFRs and other requests for information on various AD programs and initiatives to support AD in meeting stakeholder and oversight needs.

    4. Act as subject matter experts, coordinate AD-wide activities and responsibilities, and provide support to functional divisions in execution of major program activities such as recruitment and hiring, mid-year and year-end performance management, in-house and out-service training, reorganizations, labor relations, EEO and diversity, NTEU relations, office space/restack, SETR/WP&C, Employee Survey/ES Tracker, employee awards, and records management.

    5. Meet reporting requirements and execute approval responsibilities on behalf of the AD organization on various tracking and control systems such as ITRAC, webRTS, OL-5081, TRAS, HRConnect, and ITAMS.

    6. Provide general administrative support and coordination for responsibilities for AD related to maintenance of delegation orders, IRMs, OGE 450 reporting, FAIR ACT compliance, technology standards and compliance, service level agreements, maintenance of distribution lists, and telephone directories.

  3. The Pass office consists of the following groups:

    • Program Budget, Support, and Training

    • Human Resource Services

1.1.12.7.8  (04-01-2007)
Customer Service Domain

  1. The mission of the Customer Service Domain (CSD) is to enable service and communication with internal and external customers. CSD will design, develop, test, deploy, and maintain applications and systems that provide tax law assistance, taxpayer education, and access to taxpayer account data. CSD will also design, acquire, develop, test, deploy, and maintain the modernized information systems that meet customer needs in the research, update, analysis and management of taxpayer accounts. CSD is the development organization for internet applications. Services to internal and external customers are provided through five primary means:

    • Centralized Contact Centers (for telephone, written, and electronic inquiries)

    • Self-service applications (via the telephone and Internet)

    • Field Assistance (for walk-in assistance)

    • Web Services

    • Management of Taxpayer Accounts

  2. The Customer Service Domain has five subordinate offices:

    • Account Management Services

    • Customer Communications Branch

    • Integrated Data Retrieval Branch

    • E-Services Acquisition Project Office

    • Web Services, Austin Branch

1.1.12.7.8.1  (04-01-2007)
Account Management Services

  1. The mission of the Accounts Management Services (AMS) is to design, acquire, develop, test, deploy, and maintain the modernized information systems that meet customer needs in the research, update, analysis, and management of taxpayer accounts.

  2. The Accounts Management Systems has four subordinate offices:

    • I-CAM Management Branch

    • CIS/DI Core Branch

    • Requirements Management and Architecture Office

    • Program/Project Operations Office

1.1.12.7.8.2  (04-01-2007)
Customer Communications Branch

  1. The mission of the Customer Communications Branch is to plan, design, develop, test, implement, and maintain several customer communications sub-systems within the Integrated Customer Communications Environment (ICCE). ICCE provides interactive services (applications) in support of taxpayers, practitioners, and employees through multiple contact channels including telephone and the web. ICCE interactive services include Automated Self Service Applications (ASSA) that help resolve tax law, compliance, collections, refunds, and other inquiries. Where automated assistance is insufficient or not desirable, ICCE interactive services gather information from taxpayers/practitioners to help route the contact to the best possible non-automated assistance source. ICCE focuses on interactive services that require access to taxpayer account information. TRIS, CCE (CC01), Teletax, and IRFOF were merged into the ICCE program.

  2. The Customer Communications Branch has four subordinate offices:

    • Account Applications Analysis Section

    • Call Management Applications Section

    • Applications Development Section

    • Data Services Development Section

1.1.12.7.8.3  (04-01-2007)
Integrated Data Retrieval Branch

  1. The mission of the Integrated Data Retrieval Branch is to plan, design, program, schedule, implement, and maintain the Integrated Data Retrieval System (IDRS).

  2. To accomplish its mission, the Integrated Data Retrieval Branch will:

    1. Maintain Integrated Data Retrieval System (IDRS) programs including EIN Research and Assignment System (ERAS), Statutory Notice System (STN), Transcript Research System (TRS), and twenty research command codes.

    2. Provide pending transactions (prior to master file posting) on taxpayer accounts Servicewide.

  3. The Integrated Data Retrieval Branch has five subordinate offices:

    • CAF/RAF Section

    • Weekly TIF Section

    • Transcripts/ERAS Section

    • EOD Section

    • Daily TIF Section

1.1.12.7.8.4  (04-01-2007)
E-Services Acquisition Project Office

  1. The mission of the E-Services Acquisition Project Office is to:

    1. Develop, program, and enhance computer programs to support business requirements for 1120/1120S and electronic filing processing.

    2. Analyze and coordinate UWR requirements with the business operating divisions and ITS stakeholders.

    3. Perform quality systems testing and coordinate quality reviews with the ITS stakeholders and the Product Assurance organization.

    4. Provide support to the Director, Office of Professional Responsibility via the Enrolled Practitioner System (EPS), including programming and technical support.

    5. Provide programming and technical support to the National Work Planning and Control System (NWP&C) which tracks resource activity by programs against work plans (work planning and control, WP&C).

    6. Provide programming and technical support to the 6020(b) System. This role is part of the larger collection process of the IRS and requires continuing programming due to Congressional and tax law changes.

    7. Provide programming and technical support to the Workload Information Tracking System (QWIT).

    8. Provide oversight for the technical and operational activities of all web development activity in this section. This includes oversight of all web development activity, support and operation of the EUP and RUP via managed services contracts, support of the INET infrastructure and operation of its components in partnership with EO, support of applications running on INET and the web hosting environment in ECC-Detroit, and change control actions for these activities.

  2. The E-Service Acquisition Project Office has three subordinate offices:

    • E-Services Section

    • Client/Server Development Section

    • Web Development Section

1.1.12.7.8.5  (04-01-2007)
Web Services, Austin Branch

  1. The mission of the Web Services, Austin Branch includes the responsibility to convert the IRS from a location-based collaboration model to one that is based on a technology-supported virtual environment that will support the strategic goals and objectives of the IRS.

  2. The Web Services, Austin Branch will provide the following products and services:

    • Virtual meeting environment (Centra), including: Centra training, testing of updates, Centra help desk, developing training materials, testing and implementing e-Meeting features.

    • Portal and website re-design

    • Enterprise collaborative environment

    • Enterprise taxonomy design

    • Vignette content management

    • ELMS support

    • Section 508 guidance and support

  3. The Web Services, Austin Branch will provide the following support and administration:

    • Product testing and evaluation

    • Virtual classroom and meeting

    • Consultation services

    • Visioning

    • Review of new technology

    • Infrastructure design

    • Implementation of Content Management Design

    • Development and support of Enterprise Portal

    • Enterprise Collaborative Environment

    • Web Services UWR consolidation

    • Performance Support Systems

    • Security for Compliance

    • Maintain database for supported applications

    • System administration for supported applications

    • Maintain development site for testing of hardware and software

    • ELMS support

  4. The Web Services, Austin Branch has two subordinate offices:

    • Web Services, Austin Section 1

    • Web Services, Austin Section 2

1.1.12.7.9  (04-01-2007)
Test, Assurance, and Documentation Office

  1. The Test, Assurance, and Documentation Office will work in partnership with its customers to improve the quality of IRS information systems, products and services.

  2. To accomplish its mission, the Test, Assurance, and Documentation Office will:

    1. Plan, develop, schedule, and conduct systems testing of systems from the perspective of an end-user (SAT, FIT, etc.).

    2. Provide documentation and source code configuration control, integration, and system specific builds.

    3. Provide an environment for testing and integrating systems that accurately emulates the target environment.

  3. The Test, Assurance, and Documentation Office has eight subordinate offices:

    • Compliance Testing Branch

    • Internal Management Branch

    • Electronic Submission Testing Branch

    • Corporate Data Testing Branch

    • Submission Processing Testing Branch

    • Source Code and Documentation Control Branch

    • Systems Integration Branch

    • Customer Service Branch

1.1.12.7.9.1  (04-01-2007)
Compliance Testing Branch

  1. The mission of the Compliance Testing Branch is to assure customer requirements for quality systems and projects are met through established software testing practices.

  2. To accomplish its mission, the Compliance Testing Branch will:

    1. Conduct systems acceptability tests (SATs) of modernization and production systems according to guidelines outlined in IRM 2.6.1 and/or established software development life cycle processes.

    2. Independently assess the quality of application software through development of test cases, and verification through controlled data and predetermined results.

    3. Participate in analytical, design, development, and implementation reviews and coordinations.

    4. Review project documentation for clarity, consistency, accuracy, and adherence to standards.

    5. Plan, develop, schedule, and conduct SATs of tax administration and other IRS systems related to customer service, compliance, and modernization.

    6. Simulate the production environment for testing and integrating modernization and production systems.

    7. Verify and validate software requirements through all available systems documentation.

    8. Establish metrics and ensure continued success of authorized software delivered to production.

  3. The Compliance Testing Branch has five subordinate offices:

    • Collection Section

    • Compliance Services Section

    • Compliance IDRS Section

    • Examination Section

    • Ogden Compliance Section

1.1.12.7.9.2  (04-01-2007)
Internal Management Branch

  1. The mission of the Internal Management Branch is to assure customer requirements for quality systems and projects are met through established software testing practices; perform budget, program planning and execution activities; and provide testing automation for SAT.

  2. To accomplish its mission, the Internal Management Branch will:

    1. Plan, develop, schedule, and conduct acceptability tests on accounting and HR systems.

    2. Develop and maintain customized software to automate data preparation and output review.

    3. Perform budget and contract administration for the Test, Assurance, and Documentation Office, both Current Production Environment (CPE) and Modernization initiatives, including direct input to the formulation and review of applicable OMB Exhibit 300 submissions.

  3. The Internal Management Branch has four subordinate offices:

    • Accounting Section

    • SAT Automation Section

    • Budget and Contract Administration Section

    • HR Testing Section (Placeholder)

1.1.12.7.9.3  (04-01-2007)
Electronic Submission Testing Branch

  1. The mission of the Electronic Submission Testing Branch is to work in partnership with its customers to assure the quality of information systems products, and to provide data to help customers determine system readiness for nationwide production.

  2. To accomplish its mission, the Electronic Submission Testing Branch will:

    1. Review all project documentation for clarity, consistency, accuracy, and adherence to standards.

    2. Maintain critical test files according to established guidelines.

    3. Participate in Post-Implementation Reviews.

    4. Plan, develop, schedule, and conduct acceptability tests on electronic tax administration input systems processing.

    5. Simulate the production environment of new or revised systems, procedures, forms instructions, and computer programs designed to process tax returns, related documents, and various other forms of data in campuses and the ECC.

    6. Conduct all planning and testing activities in accordance with IRM 2.6.1.

  3. The Electronic Submission Testing Branch has four subordinate offices:

    • 1041/1065 ELF Section

    • Submission Input Section

    • BMF ELF Section

    • IMF/ELF/Electronic Remittance Section

1.1.12.7.9.4  (04-01-2007)
Corporate Data Testing Branch

  1. The mission of the Corporate Data Testing Branch is to work in partnership with business customers and software developers to continually improve corporate software systems, products, and services.

  2. To accomplish its mission, the Corporate Data Testing Branch will:

    1. Review, analyze, and assess customer requirements.

    2. Issue test plans to communicate scope, constraints, time-lines, and known and potential risks.

    3. Determine conditions to effectively validate customer requirements, create test cases and test data to validate each condition.

    4. Execute test, research failures and capture results.

    5. Ensure requirements traceability to design and software.

    6. Status with partners test progress against schedule, issue a formal report of test findings and perform close out activities.

  3. The Corporate Data Testing Branch has four subordinate offices and one modernization project office:

    • BMF Testing Section

    • IMF Testing Section

    • MF Notices Testing Section

    • Tax Data Online Testing Section

    • CADE Project Office

1.1.12.7.9.5  (04-01-2007)
Submission Processing Testing Branch

  1. The mission of the Submission Processing Testing Branch is to work in partnership with our customers to continually improve the quality of the IRS information systems, products, and services.

  2. To accomplish its mission, the Submission Processing Testing Branch will:

    1. Plan, develop, schedule, and conduct SATs of tax administration processing systems using dedicated test platforms to simulate the production environment of new or revised systems.

    2. Ensure the needs of our customers are met by adhering to processes and procedures in IRM 2.6.1 (PA) and IRS Standards.

    3. Empower each employee to accomplish SAT in an effective and efficient manner.

  3. The Submission Processing Testing Branch has three subordinate offices:

    • BMF SC Section

    • MeF Section

    • IMF SC Section

1.1.12.7.9.6  (04-01-2007)
Source Code and Documentation Control Branch

  1. The mission of the Source Code and Documentation Control Branch is to use comprehensive software and documentation version control procedures to ensure that only approved application code and associated documentation are provided to SAT, FIT, and Production, implement security across Test, Assurance and Documentation, and implement Configuration Management for Business Systems Development.

  2. To accomplish its mission, the Source Code and Documentation Control Branch will:

    1. Provide independent source code and documentation control of the Service’s critical systems and implement consistent control tools for all environments.

    2. Build and promote transmittals and application baselines to SAT, FIT, and Production environments for all tiers.

    3. Provide web and database support.

    4. Coordinate all PA security issues including the Security Certification and Accreditation of Test, Assurance and Documentation Systems.

    5. Coordinate and implement Configuration Management Control Boards and verify execution of CM plans throughout AD.

  3. The Source Code and Documentation Control Branch has four subordinate offices:

    • Documentation Repository Section

    • Tier 1 Configuration Section

    • Tier 2 and 3 Configuration Section

    • Transmittal Build Section

1.1.12.7.9.7  (04-01-2007)
Systems Integration Branch

  1. The mission of the Systems Integration Branch is to work with our partners and customers to improve the quality of the IRS IT products and services.

  2. To accomplish its mission, the Systems Integration Branch will:

    1. Implement, provide oversight, and manage the environments that emulate the target production environments for testing activities for SAT, FIT, and Modernization projects.

    2. Plan and execute the Final Integration Test (FIT).

    3. Support management and the testing organizations with measuring and reporting the progress of the TAD efforts.

  3. The Systems Integration Branch has three subordinate offices:

    • Test Integration Section

    • Tier 2 Test Administration Section

    • FIT Section

1.1.12.7.9.8  (04-01-2007)
Customer Service Branch

  1. The mission of the Customer Service Branch is to assure customer requirements for quality systems and projects are met through established software testing procedures for each system tested prior to nationwide Production release.

  2. To accomplish its mission, the Customer Service Branch will:

    1. Conduct systems acceptability tests (SATs) of modernization and production systems according to guidelines outlined in IRM 2.6.1 and/or established software development life cycle processes.

    2. Independently assess the quality of application software through development of test cases, and verification through controlled data and predetermined results.

    3. Prepare test plans, periodic status reports, End of Test Status Reports, and other test documents required by IRM 2.6.1.

    4. Participate in design and developmental progress reviews (e.g., coordinations and walkthroughs) and coordinate Test Readiness Reviews and Post-Implementation Reviews.

    5. Review documentation for clarity, consistency, accuracy, and adherence to standards.

    6. Prepare test data and predetermined results based on project documentation and requirements.

    7. Execute test, perform output review, document and track deficiencies using ITAMS, and perform regression testing on program changes.

    8. Maintain critical test files, project folders, and test logs according to IRM 2.6.1.

  3. The Customer Service Branch has three subordinate offices:

    • E-Services Section

    • Customer Service IDRS Section

    • Customer Communication Section

1.1.12.8  (04-01-2007)
Associate Chief Information Officer for Enterprise Services

  1. The mission of Enterprise Services is to enable business transformation through integrated solutions, services, and standards.

  2. Enterprise Services has two subordinate offices:

    • Business Integration

    • Systems Integration

1.1.12.8.1  (04-01-2007)
Business Integration

  1. The mission of Business Integration is to enable business transformation by providing integrated solutions, services, and standards. Business Integration is a strategic partner to the business owners and provides support and services on an enterprise level.

  2. To accomplish its mission, Business Integration will:

    1. Partner with business customers to fully understand business objectives, priorities, and needs.

    2. Match MITS support and services to the business needs and integrate service delivery components.

    3. Develop strategies and release plans designed to fulfill the business needs.

    4. Facilitate priorities and direction in establishing a multi-year investment portfolio.

    5. Provide solution concepts and full life-cycle costing to better define the portfolio.

    6. Identify and communicate resource implications of the IT portfolio.

    7. Manage all demand for MITS support and services, ensuring all work is strategically aligned.

    8. Facilitate and/or support prioritization.

    9. Formulate and provide baseline control of the IT modernization budget.