Skip Navigation  
acfbanner  
blueline
Department of Health and Human Services 
		  
		  Administration for Children and Families
          
ACF Home   |   Services   |   Working with ACF   |   Policy/Planning   |   About ACF   |   ACF News   |   HHS Home

  Questions?  |  Privacy  |  Site Index  |  Contact Us  |  Download Reader™Download Reader  |  Print Print      

National Human Services IT Resource Center

CSE Internal Scanning Worksheet

Click here to download the MS Word (33.5 KB)

  1. Purpose:
    1. To summarize the interfaces between CSE internal entities and the IT Division, noting the relationships in terms of the responsibilities and dependencies. This leads to an understanding of the influences the internal entities and the IT Division exert on one another. For strategic planning purposes, it is not necessary to define each interface precisely, only to identify and characterize them in terms of the types of information exchanged. This includes an understanding of the relationships among CSE's internal entities, as well as between these entities and the HS IT Division.
    2. Each row should include a reference to the source data that was used to develop the summary. This source data could take any form, such as a report, presentation, Web site, or an individual.

  2. Instructions:
    1. Column 1 lists the internal entities (e.g., programs, organizational structures, or individuals within CSE scope).
    2. Column 2 lists the CSE business function that requires the interface.
    3. Column 3 lists the communication protocol used (e.g., TCP/IP).
    4. Column 4 lists the responsibilities the IT Division has to the entity (what goes out of the IT Division).  Responsibilities indicate objects (technology resources, information services, reports, etc.) that the entity expects to receive from the IT Division (e.g., standard software applications on all users workstations).
    5. Column 5 gives the dependencies the IT Division has on the entity (what comes into the IT Division). Dependencies indicate objects (e.g., funding, IT needs, facilities) that CSE provides to the IT Division (e.g., functional requirements, policy or interpretations of Federal law).
    6. Column 6 lists the constraints on the interfaces, responsibilities, or dependencies that originate within CSE, possibly in reaction to constraints imposed from outside the HS Agency (e.g., Human Resource policy, budgets, contracting law, staffing).
    7. Column 7 documents any quality measures or perceptions about the interface or associated support (such as that gained from user surveys). Consider whether the information is passed in a timely manner, whether it is accurate, or whether it is presented in a usable form.
    8. Column 8 describes the relationships.
    9. Column 9 lists potential changes to an entity or the relationship. This may include organizational changes or changes to ongoing programs. For each possible change, include the following:

      i. Expected timeframe

      ii. Likelihood of occurring

    10. Column 10 is for collecting other information about the entity that might impact either CSE or the IT Division.
  3. All entities listed in the Internal Environment Data Collection Plan Worksheet must be described.
  4. Use the CSE Interface Types Worksheet to assist you in your collection efforts.

Example - Internal Scanning Worksheet

1. Internal Entity

2. CSE Business Function

3. Interface Protocol and Data Format

4. Responsibilities M = Manual E = Electronic

5. Dependencies

6. Constraints

7. Perceived Quality

8. Relationships 9. Potential Changes 10. Other

County Courts

Support Orders

M = paper report

E. Inform case workers of support order.

Accuracy of support information

Maximum support amounts permitted under the Consumer Credit Protection Act

Data is not always received in a timely fashion.

State Disbursement Unit

Automated interfaces with courts

L = Will probably happen

T = FY 2004

Not all support orders are for money.


Internal Scanning Worksheet

1. Internal Entity

2. CSE Business Function

3. Interface Protocol and Data Format

4. Responsibilities M = Manual E = Electronic

5. Dependencies

6. Constraints

7. Perceived Quality

8. Relationships 9. Potential Changes 10. Other












                 












                 


Last Updated: May 4, 2005