United States Department of the Interior

![](media/image1.png){width="1.9354166666666666in"
height="1.8354166666666667in"}

DEAR Integrated Project Team

Charter

**May 21, 2004 \-- DRAFT**

# [Purpose]{.underline}. 

The purpose of Department of the Interior (DOI) Enterprise Architecture
Repository (DEAR) Integrated Project Team (IPT) is to review issues and
make recommendations with respect to implementation, enhancement, and
use of DEAR.

# [Background]{.underline}.

DOI is required to compile and maintain the Interior Enterprise
Architecture (IEA) in accord with the Federal Enterprise Architecture
(FEA). The IEA is maintained in DEAR. Conformance to the FEA is required
for approval of information technology (IT) system investments in the
annual budget process. The objective is to reduce needless redundancies,
inconsistencies, inefficiencies and costs associated with IT systems by
which data is generated, compiled, shared, analyzed, processed,
maintained and used to conduct business on a Governmentwide basis. The
FEA and IEA identify cross-cutting IT functions and, thus, opportunities
for joint investment to reduce costs and increase efficiency and
effectiveness. The software supporting DEAR is Popkin System Architect
(PSA).

# [Scope]{.underline}. 

DEAR is the official system of record for architectural information
concerning all DOI tracked systems. The IPT reviews proposed
modifications to the software and the structure of the database
supporting DEAR. The IPT will also consider and make recommendations
concerning the sharing of data among DEAR and other systems.

The bureaus are responsible for maintaining their own bureau-level
instances of the enterprise architecture repository (BEARs) consistent
with the architecture of DEAR and the need to share data with other
systems.

# [Roles and Responsibilities]{.underline}.

The IPT reviews issues brought to its attention and makes
recommendations to the Chief Architect concerning the design, planning,
deployment and enhancement of DEAR.

Working with DOI cross-cutting teams for security, configuration
management, capital planning and investment control as well as the
Interior Business Architecture Team (IBAT), Interior Architecture
Working Group (IAWG), and Indian Trust Architecture Review Board, the
IPT will provide a focal point for issues and recommendations to ensure
DEAR is effectively implemented throughout DOI, including its bureaus
and offices, to provide an integrated information repository and
analytical tool to support the IEA.

The IPT is responsible for:

1.  Reviewing and recommending changes to the structure of the DEAR
    metamodel.

2.  Recommending changes in the logical and physical architectures for
    deployment of DEAR throughout DOI, including the sharing of data
    with other systems.

3.  Identifying potential users of DEAR and considering PSA licensing
    issues.

4.  Recommending strategies to optimize the usability and utility of
    DEAR, including access to and use of the data it contains.

5.  Reviewing and recommending enhancements to DEAR.

6.  Coordination with other government users of PSA with respect to its
    features and functionality, including its ability to share data with
    the Federal Enterprise Architecture Management System (FEAMS).

# [IPT Composition and Function]{.underline}. 

The IPT is comprised of 12 voting members with the following roles and
expertise:

1.  Chief Architect

2.  DEAR Program Manager, Permanent Co-Chair

3.  Architecture, Bureau Member

4.  Security, DOI Member

5.  Security, Bureau Member

6.  Capital Planning & Investment Control (CPIC), DOI Member

7.  CPIC, Bureau Member

8.  Business Process, Office of the Secretary (OSD)

9.  Business Process, Policy Planning Management (PPM)

10. Business Process, Bureau Member

11. Indian Trust

12. Configuration Management, Bureau Member

A co-chair will be appointed by the DEAR Program Manager. DEAR
contractor staff may participate in an advisory capacity. Procedures
under which the IPT will operate include:

1.  Meetings will be scheduled as needed by the co-chairs.

2.  Meeting agendas and background material will be posted on the IEA
    website and distributed to membership prior to each meeting.

3.  Minutes of each meeting will be posted on the IEA website.

4.  Recommendations will be conveyed to the Chief Architect.

5.  As approved by the Chief Architect, the DEAR Program Manager will
    direct changes and enhancements to the PSA software or database
    structure.

```{=html}
<!-- -->
```
I.  **[IPT Co-Chair Responsibilities]{.underline}**

The IPT is led by the co-chairs, who provide leadership for the team's
activities and products, including:

1.  Scheduling and directing IPT meetings and activities.

2.  Serving as the team's representatives and spokespersons.

3.  Ensuring adherence to the processes and procedures defined by the
    team.

4.  Conveying recommendations to the Chief Architect.

5.  Directing implementation of recommendations approved by the Chief
    Architect.

```{=html}
<!-- -->
```
II. **[IPT Member Responsibilities]{.underline}**

Each IPT member will:

1.  Actively participate in IPT meetings and activities.

2.  Encourage stewardship of and commitment to the mission, vision and
    objectives of the team.

3.  Adhere to IPT decisions, processes, and procedures.

4.  Represent the interests of their organization fairly and openly in
    an effort to develop decisions based on an enterprise versus
    organizational perspective.

5.  Facilitate communication and the free exchange of ideas with team
    members.

6.  Provide operational and technical expertise in areas relevant to
    their knowledge/background.

7.  Serve as point of contact for their respective organization.

8.  Review documentation and provide feedback as necessary.

```{=html}
<!-- -->
```
III. **[IPT Relationships with other Teams/Boards]{.underline}**

The co-chairs will monitor activities by other groups that may be
relevant to the responsibilities of the IPT and will advise the members
of such activities. Particular attention will be paid to activities
related to systems with which DEAR needs to share data. Recommendations
made by the IPT will be conveyed to the Chief Architect, who will
determine and direct interaction with other DOI organizations as
necessary and appropriate.

IV. **[Communication]{.underline}**

Notice of each meeting will be distributed to members and other
participants via E-mail. Meeting agendas, minutes, and related
information will be posted on the IPT website.
<http://www.doi.gov/ocio/architecture/ipt.htm> Members and other
participants will advise the co-chairs of issues they believe should be
addressed by the group.

V.  **[IPT Decision Authority]{.underline}**

The IPT reports to the Chief Architect, who determines what, if any,
action to take on recommendations made by the group.

VI. **[IPT Decisions]{.underline}**

Decisions will generally be made by consensus. If consensus is not
possible on any issue, it may be put to a vote by the co-chairs, in
which case a simple majority of the voting members will be required for
approval. A quorum of seven voting members shall be required to decide
any issue on which consensus is not achieved among those participating
in any meeting.

1.  The co-chairs will appoint voting members.

```{=html}
<!-- -->
```
2.  Non-voting participants may engage in discussion and
    consensus-building.

3.  Each participant's expenses will be the responsibility of his or her
    sponsoring agency.

4.  Each voting member will have one vote.

5.  Tie votes will be resolved by the Chief Architect.

# [Approved By]{.underline}: 

This Charter is effective as of the date of approval by the CIO. The
Charter may be revised as necessary by the co-chairs of the IPT with
approval of the Chief Architect and the CIO.

**Approved by:**

W. Hord Tipton
(CIO)\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Date