- CWPM Home
- 1. AFCARS
- 2. CAPTA
- 3. Independent Living
- 4. MEPA/IEAP
- 5. Monitoring
- 6. CCWIS
- 7. Title IV-B
- 8. Title IV-E
- 9. Tribes/Indian Tribal Organizations
- Search the Child Welfare Policy Manual
- Additional Resources
- User Guide
- Withdrawn Child Welfare Policies
- References
- Print the Manual
- Additions to the Manual
- Deletions to the Manual
- Modifications to the Manual
- Cumulative Change History of Questions & Answers
6.12A.4. Reuse
Answer
There are two general processes by which title IV-E agencies may share components.
First, ACF may request software and associated documents for the federal repository per requirements at paragraph 1355.52(h). ACF may then share these products with title IV-E agencies at the agency's request.
Second, title IV-E agencies may directly share products with other agencies.
Source/Date
1/11/2017
Legal and Related References
45 CFR 1355.53; 81 FR 35450 at 35470 (issued June 2, 2016); 80 FR 48200 at 48217 - 48218 (issued August 11, 2015)
Answer
No, paragraph 1355.53(a)(4) does not require title IV-E agencies to make automated functions adaptable to different hardware configurations without manual configuration (plug and play).
Source/Date
1/11/2017
Legal and Related References
45 CFR 1355.53; 81 FR 35450 at 35470 (issued June 2, 2016); 80 FR 48200 at 48217 - 48218 (issued August 11, 2015)
Answer
No. Paragraph 1355.53(a)(4) requires that automated functions be "capable of being shared, leveraged, and reused." The regulation does not require modules be reused when it is not appropriate, such as when a module does not support an agency's business processes.
Source/Date
1/11/2017
Legal and Related References
45 CFR 1355.53; 81 FR 35450 at 35470 (issued June 2, 2016); 80 FR 48200 at 48217 - 48218 (issued August 11, 2015)