Responsive Document - CREW: Army Corps of Engineers: Regarding Record Management and Cloud Computing: 4/26/2012 - HQDA Pages - Binder

8/2/2019 Responsive Document - CREW: Army Corps of Engineers: Regarding Record Management and Cloud Computing: 4

1/42

AMERICAS ARMY:

THE STRENGTH OF THE NATION

UNCLASS/FOUO

72 comments, 26 pages total

18 Critical: 7 rejected (POA&M or Migration Scheduleappropriate, not EXORD)

12 Rejected: Most are not germane to the base EXORD canbe addressed with the Implementation Plan

13 General comments and questions for CIO/G-6 andARCYBER / NETCOM consideration can be addressed withthe Implementation Plan

1 Defer to the EGB / LWN GOSC Secretariat to address

Recommend the Reserve Component (Army Reserve & National Guard) be

added as voting member in the review processes for enterprise emailapplication and services through the existing Enterprise ConfigurationManagement and Operations Oversight Board to the Reserve Componentequities are validated.

Results of O-6 Coordination


2/42


3/42


4/42


5/42


6/42


7/42


8/42


9/42


10/42


11/42


12/42


13/42

UNCLASSIFIED//FOR OFFICIAL USE ONLYDRAFT - 2/3-Star review 2 Dec 2010

UNCLASSIFIED//FOR OFFICIAL USE ONLY

Copy__of__Copies1Headquarters, Department of the Army2

Pentagon, Washington, DC34

HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC)5

Implementation Army Migration to DoD Enterprise Email Services67

(U//FOUO) References:89

a. (U) Memorandum, Chief of Staff of the Army (CSA), subject: LandWarNet 10Global Network Enterprise Construct Strategy Implementation, dated 2 March 2009.11

12

b. (U) Memorandum, Army CIO/G-6, Global Network Enterprise Construct 13Transformation of LandWarNet, dated 24 June 2009.14

15

c. (U) HQDA, Planning Order (PLANORD): LandWarNet Global Network16

Enterprise Construct (GNEC) Implementation, ALARACT 292/2009, dated 19 October172009.18

19

d. (U) Army Enterprise Infrastructure Directory Services Naming Conventions and20Standards Version 5.1, dated 1 February 2007.21

22

e. (U) DoD Instruction 8551.1, Ports, Protocols, and Services Management, dated2313 August 200424

25

f. (FOUO) DoD Ports, Protocols, and Services Management (DoD-PPSM)26Exception Management Process, dated 22 June 2010.27

28g. (U) General Order 5, Establishment of U.S. Army Network Enterprise Technology29

Command/9th Army Signal Command, dated 13 August 2002.3031

h. (U) General Order 2010-26, Establishment of the United States Army Cyber32Command, dated 1 October 2010.33

34

i. (U) Memorandum, Under Secretary of the Army, subject: Guidance on35Implementing Army Efficiency Initiatives, dated 2 September 2010.36

37

j. (U) Execute Order (EXORD) 259-10: Campaign on Property Accountability,38

ALARACT 210/2010, dated 09 July 2010.3940

k. (U) AR 25-1, Army Knowledge Management and Information Technology, dated 441December 2008.42

43

l. (U) DA Pamphlet 25-1-1, Information Technology Support and Services, dated 2544October 2006.45

46


14/42


HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC)Implementation Army Migration to DoD Enterprise Email Services

2

1. (U) Situation.47

a. (U) A CSA memo (reference a) established the Global Network Enterprise48Construct as the strategy to transform LandWarNet (LWN) into an Army Enterprise49framework and designated NETCOM/9th Signal Command (Army) (NETCOM/9th SC(A))50as the Army's enterprise network manager for Generating Force networks. GNEC51supports four strategic objectives: 1) enabling warfighting capabilities through the52Network; 2) dramatically improving network defense; 3) realizing efficiencies while53improving effectiveness; and 4) ensuring Army interoperability with the Department of54Defense. Since publishing the CSA memo, the Under Secretary of the Army has55directed that information technology (IT) efficiencies be obtained to meet cost savings56for FYs 2012-16, specifically, the migration to an Enterprise Email capability and Army57data center consolidation (reference i). This EXORD directs Army Enterprise Email58

migration.5960

b. (U) The scope of this effort includes all Non-secure and Secret Internet Protocol61Router Network (NIPRNet and SIPRNet) Exchange systems with the exception of those62that deploy with operating forces.63

64

2. (U) Mission. The Army will migrate to the Defense Information Systems Agency65(DISA) Enterprise Email service no later than (NLT) 1 October 2011, providing users66access to the Enterprise any time from any CAC-enabled computer. End state will be67achieved when Army Cyber Command (ARCYBER) reports that all Army email services68are being provided through a single DoD enterprise-level email service.69

703. (U) Execution.71

72

a. (U)Intent. The CSA directed that LandWarNet be transformed into a73centralized, more secure, operationalized and sustainable network, capable of74supporting an expeditionary Army and making daily operations more efficient. To75achieve this goal, the Army will establish conditions and processes that provide76ARCYBER a better understanding of all Army email requirements and enable their77consolidation under a single DoD enterprise-level email service.78

79

b. (U) Concept of Operations. Army migration to DoD enterprise email services will80

be conducted in three phases: Phase 1, Discovery; Phase 2, Planning; and Phase 3,81Execution. In accordance with (IAW) the September 2010 CIO/G-6 Army Enterprise82Guidance Board (EGB) decision, these phases may be conducted in parallel between83different installations.84

85

(1) Phase 1, Discovery. ARCYBER will conduct Discovery activities that support86transition planning for Enterprise objectives by determining the as-is, or current, state87of Army email requirements and services. All Army organizations will provide the88


15/42



3

required data as specified in Annex A (Migration POC and Services Data Call) to89NETCOM/9th SC(A) through ARCYBER NLT 30 days after receipt of this EXORD. Data90

requested, collected and submitted must be classified no higher than Unclassified//For91Official Use Only (U//FOUO). This phase must be finished prior to completing a Plan of92Action and Milestones (POA&M) in Phase 2. This phase is complete for the Army93Enterprise when ARCYBER reports that all organizations have complied with the data94call.95

96

(2) Phase 2 (Planning): ARCYBER in coordination with (ICW) Army Commands,97Army Service Component Commands and Direct Reporting Units will conduct enterprise98email service migration planning to: determine the commands and units that will be99subject to this order and the level of effort for each organization; and identify any100

potential resource shortfalls. Every organization currently providing email services will101develop a POA&M for migration to the DoD Enterprise Email Service. Subject102organizations will also start to prepare for migration to enterprise email services (e.g.,103reduce mailbox sizes IAW instructions listed in Annex C) IAW technical guidance to be104published by ARCYBER NLT 15 December 2010. This phase is complete for an105organization when the POA&M, including the detailed site migration schedule, has been106validated by ARCYBER. The goal for completing this phase is NLT 30 days prior to the107start of Phase 3 (Execution) for each organization.108

(3) Phase 3 (Execution): Under the direction of ARCYBER, all Army109organizations will transition organic email services to the DoD Enterprise Email Service110

NLT 1 October 2011. HQDA begins implementation 1 February 2011, followed by the111rest of the Army. A detailed schedule will be published NLT 90 days after the effective112date of this EXORD. Any organizations seeking an extension to complete tasks for113email service migration will send the request to Commander, ARCYBER (ATTN: NETC-114CG). Organizations that have an existing formal agreement with HQDA for a migration115date after 1 October 2011 must re-submit their extension request IAW para 3.d.(1).116This phase is complete when ARCYBER reports that all Army email services are being117provided through a single DoD enterprise-level email service.118

119

c. (U) Tasks.120121

(1) (U) HQDA, G-3/5/7122123

(a) Monitor the waiver process and maintain visibility of all POA&Ms124submitted to ARCYBER.125

126

(b) Conduct monthly in-progress reviews (IPRs) with ARCYBER, CIO/G-6127and NETCOM/9th SC(A) to ensure that Army enterprise email requirements and128specifications are being met.129


16/42



4

130

(2) (U) HQDA, CIO/G-6131

132(a) ICW HQDA G-3/5/7, ARCYBER AND NETCOM/9th SC(A), coordinate all133

resource issues and/or requirements with the Defense Information Systems Agency134(DISA).135

136

(b) Monitor the waiver process and maintain visibility of all POA&Ms137submitted to ARCYBER NETOPS. Provide details to ARCYBER for all existing138agreements between HQDA and organizations that exempt the organization from139meeting the 1 October 2011 suspense for Enterprise Email migration.140

141

(c) Provide cost recovery schedule 8 to HQDA G-8 Program Analysis and142

Evaluation and the Assistant Secretary of the Army (Financial Management and143Comptroller) (Army Budget Office) by 15 December 2010. Schedule 8 will include all144commands currently providing email, establish an Enterprise Email budget line (MDEP145MSNS, SAG 432) and provide accountability for projected email efficiency.146

147

(3) (U) ARCYBER148149

(a) Act as the Army lead for migration planning, develop detailed site-level150migration schedules and assist sites in the actual migration to the DoD Enterprise Email151Service.152

153

(b) Review, validate and track submitted POA&Ms from all organizations.154155

(c) Review and adjudicate all submitted waiver requests from all156organizations within 14 days of receipt from the requesting organization.157

158

(d) Provide monthly updates to G-3/5/7 and CIO/G-6 on migration status, to159include POA&M and extension waiver issues.160

161

(e) Ensure the Army Operations Oversight Board (OOB) conducts periodic162updates during its scheduled events and assesses operational impacts to the163enterprise.164

165(f) Participate in monthly IPRs with all stakeholders to ensure completion of166

tasks and continuity throughout.167168

(g) Act as the overall technical lead and project manager for migration to169DoD Enterprise E-Mail Services and coordinate unique organization requirements with170CIO/G-6 and DISA.171

172


17/42



5

(h) Develop, maintain content for and provide access to the Enterprise E-173Mail web site (https://www.intelink.gov/inteldocs/browse.php?ffolderid=19731/)174

throughout the migration process. Users must have an Intelink Passport account to175access the documentation. (Follow the instructions on the initial page if you have not176previously registered at this site.)177

178

(i) Develop and publish enterprise email public folder guidance, client179configuration and implementation guidance NLT 45 days after effective date of this180EXORD.181

182

(j) ICW CIO/G-6 and DISA, ensure Information Assurance (IA) guidance is183developed and published.184

185

(k) ICW Army organizations currently using an Exchange e-mail capability,186develop and publish guidance for the creation of command-specific Installation187Sequence Lists (ISLs) to be used throughout the planning and migration process. The188document template is in Annex B (Installation Sequence List (ISL) Document Template)189and at the Enterprise E-Mail web site listed above.190

191

(l) Evaluate and consolidate NIPRNet and SIPRNet requirements, evaluate192applications, and coordinate approval and adoption of those meeting existing/emerging193enterprise criteria.194

195

(m) Participate as a voting member in the review processes for enterprise196

email application and services through the existing Enterprise Configuration197Management and Operations Oversight Board.198

199

(n) Establish tactics, techniques and procedures for Army responsibilities200related to deployment, operation and management of DoD Enterprise Email and201supporting mobile services (to include publishing the plan for deployment of edge nodes202in coordination with DISA).203

204

(4) (U) Army Organizations. Subject commands and units determined in Phase2052 of this operation will:206

207

(a) Every organization currently providing email services will develop a208POA&M for migration to the DoD Enterprise Email Service.209

210

(b) Participate in HQDA and/or ARCYBER working groups as required to211execute tasks in this EXORD.212

213

(c) Provide a primary and an alternate POC for this EXORD to the CIO/G-6214and ARCYBER POCs NLT seven days after receipt of this EXORD.215


18/42



6

216

(d) Implement and report status of mailbox resizing efforts (Annex C) to217

ARCYBER (ATTN: NETC-CG) on a weekly basis until in full compliance.218219

(e) Submit completed Migration Checklist IAW Annex A to ARCYBER220(ATTN: NETC-CG) NLT 45 days after receipt of this EXORD. Once Annex A data are221submitted, no additional changes to mailbox-enabled applications or additions of new222public folders should be made. Any operationally required changes must be reported to223the ARCYBER POC.224

225

(f) Validate or make recommendations for changes to Installation Sequence226List (Annex B) to ARCYBER (ATT: NETC-CG) NLT 45 days after receipt of this227EXORD.228

229(g) If required, submit waiver requests for extension to task(s) in this230

EXORD, along with associated POA&M, to Commander, ARCYBER (ATTN: NETC-CG)231NLT 14 days after receipt of this EXORD. All requests must clearly describe why the232extension is required and why it is in the Armys best interest to grant the extension.233The waiver request must include: an updated POA&M that clearly articulates the234situation causing the delay; proposed remedial actions; estimated completion date and235associated time lines; and a primary and alternate POC (name, phone number and e-236mail address).237

238

(h) Ensure all organic user (Windows) workstations and laptops accessing239

DoD Enterprise Email are configured within the following requirements: AGM Windows240Vista SP2 (or newer), AGM Office 2007 SP2, AGM Tumbleweed Desktop Validator 4.10241and AGM Activclient 6.2. Failure to meet this requirement will result in the inability to242access the DoD Email Service.243

244

(i) Ensure all organic Microsoft Exchange mailbox servers have a recent245backup and have had database maintenance performed within 30 days of scheduled246migration date.247

248

(j) Migrate organic mailboxes from existing systems into the DoD Enterprise249Email Service in accordance with established Installation Sequence Lists.250

251(k) Ensure that all organic users who require a SIPRNET email account (and252

do not already have an AKO-S account) register for an AKO-S account NLT 15 JAN2532011. This will enable accurate identification and provisioning of all users who require a254SIPR email account in the SIPR enterprise email service. Report status of AKO-S255registration efforts to ARCYBER (ATTN: NETC-CG) on a weekly basis until 16 Jan2562011.257

258


19/42



7

d. Coordinating Instructions.259260

(1) (U) Organizations with existing waivers must re-submit to ARCYBER for re-261validation within 14 days after receipt of this EXORD. The waiver request must include262an updated POA&M that clearly articulates the situation causing the delay, proposed263remedial actions, estimated completion date and associated time lines, and a primary264and alternate POC (name, phone number and e-mail address).265

266

(2) (U) General guidance for reducing mailbox sizes in preparation for migration267is listed in Annex C (Guidance on Reducing Mailbox Sizes).268

269

(3) (U) The migration checklist template in Annex A (Migration POC and270Services Data Call) will be used to ensure readiness prior to migration. A Migration271

Coordination Team, comprised of subject matter experts (SMEs) from ARCYBER,272NETCOM/9th SC(A) and other organizations, as required, may conduct an on-site273integration coordination visit to validate the organization/site baseline prior to executing274migration.275

276

(4) (U) Army National Guard retains responsibility to coordinate waivers for277NIPRNET and SIPRNET Generating Force Title 32 email services.278

279

(5) (U) U.S. Army Special Operations Command (USASOC) retains the280responsibility to coordinate waivers for NIPRNET and SIPRNET Special Operating281Forces Information Enterprise (SIE) email services.282

283(6) (U) NLT seven days after receipt of this EXORD, all tasked organizations will284

acknowledge receipt of this EXORD and provide contact information for designated O-6285level and action officer points of contact to the contacts listed in paragraph 5b.286

287

4. (U) Service and Support.288289

a. (U) Support Concept.290291

b. (U) Materiel and services.292293

(1) Equipment disposition guidance.294295

(a) (U) IAW EXORD 259-10, Campaign on Property Accountability296(reference j) units are to identify excess IT equipment after migration to DoD Enterprise297Email Services.298

299

(b) (U) IT equipment declared excess as a result of the Enterprise Email300migration may be reutilized as a lifecycle replacement and the replaced equipment will301


20/42



8

then be declared excess. Excess IT equipment will be disposed of IAW AR 25-1302(reference k) paragraph 6-2.k (Redistribution and disposal of IT assets), DA Pamphlet303

25-1-1 (reference l) paragraph 11-3 (Redistribution and disposal of IT assets) and304command guidance.305

306

5. (U) Command and Signal.307308

a. (U) ARCYBER is the supported command for the purposes of this EXORD.309310

(1) (U) Strategic communications for this initiative are the responsibility of311CIO/G-6.312

313

(2) (U) DIRLAUTH with ARCYBER is authorized.314

315b. (U) Points of Contact.316

317

(1) (U) G-3/5/7 LWN/BC: Ms. Maria Drew, (703) 545-2554 [email protected]; and Mr. Michael Dowdy, (703) 545-2601 [email protected]

(2) (U) CIO/G-6 AONS: LTC Peter Barclay, (703) 602-9250 [email protected]; and Mr. Thomas Trucks, (703) 806-4224 [email protected]

(3) (U) ARCYBER: COL William "Max" Duggan, (703) 706-2850 [email protected]

326

(4) (U) NETCOM/9th SC(A): Mr. Michael Bomba, (520) 538-6278 [email protected]; Mr. Raymond Turcotte, (520) 538-3733 [email protected], and Mr. Kevin Mott, (520) 538-6530 [email protected]

331

332

333

334

335ACKNOWLEDGE: GEORGE W. CASEY, JR.336

General, United States Army337Chief of Staff338

OFFICIAL339340

341

342


21/42



9

343

DANIEL P. BOLGER344

Lieutenant General, GS345Deputy Chief of Staff, G-3/5/7346

347

DISTRIBUTION:348Principal Officials of Headquarters, Department of the Army349Commander350

U.S. Army Forces Command351U.S. Army Training and Doctrine Command352U.S. Army Materiel Command353U.S. Army Europe354U.S. Army Central355

U.S. Army North356U.S. Army South357U.S. Army Pacific358U.S. Army Special Operations Command359Military Surface Deployment and Distribution Command360U.S. Army Space and Missile Defense Command/Army Strategic Command361Eighth U.S. Army362U.S. Army Network Enterprise Technology Command/9th Signal Command (Army)363U.S. Army Medical Command364U.S. Army Intelligence and Security Command365U.S. Army Criminal Investigation Command366

U.S. Army Corps of Engineers367U.S. Army Military District of Washington368U.S. Army Test and Evaluation Command369U.S. Army Reserve Command370U.S. Army Installation Management Command371

Superintendent, United States Military Academy372Director, U.S. Army Acquisition Support Center373U.S. Army Accessions Command374Deputy Under Secretary of the Army (Business Transformation)375Director, Small and Disadvantaged Business Utilization376Director, Enterprise Task Force377

378379

380

381


22/42


Annex A (Migration Points of Contact (POC) and Services Data Call) to HQDA EXORD,LandWarNet Global Network Enterprise Construct (GNEC) Implementation ArmyMigration to DoD Enterprise Email Services

UNCLASSIFIED//FOR OFFICIAL USE ONLYA-1

1

NO INTERNET PROTOCOL OR DERIVATIVE CLASSIFICATION INFORMATION IS2

TO BE PROVIDED34

5

ACTION: Complete information below. List Primary (P) and Alternate (A) POCs for6your organization, theater operations and each NEC-like facility.7

8

ORGANIZATION NAME: ___________________________9POINTS OF CONTACT FOR ENTERPRISE EMAIL:10

11

POC NAME PHONE AKO EMAIL

ORGANIZATION (P)ORGANIZATION (A)

THEATER (P)

THEATER (A)

NEC [NAME] (P)

NEC [NAME] (A)

IMPORTANT NOTICE: REPEAT NEC AND THEATER ROWS AS NECESSARY.12

13

UNIQUE P RODUCTS AND SERVICES :14

Identify any applications (include manufacturer and version number) or services that15provide unique capabilities that may affect transition to an Enterprise E-Mail Service.16

17

SITE ACCESS INFORMATION. Please provide the POC (Security Managers) to obtain18access to your installations, facilities and server rooms (each, as necessary):19

20

LOCATION NAME EMAIL PHONE NUMBER

(P)(A)

21

22


23/42



A-2

EMAIL BASELINE CHECKLIST23

241. Approximately how many users on SIPRNET (per location)?25

26LOCATION NUMBER

OFUSERS

CURRENT STORAGEAMOUNT/MAILBOXSIZE?

DO YOUHAVE ANYPUBLICFOLDERS?

TOTALAMOUNT OFDATA INTHE PUBLICFOLDERS

IDENTIFY ALLSPECIALINTERESTCUSTOMERS

27

2. Approximately how many organizational and resource mailboxes on SIPRNET (per28

location)?2930

LOCATION NUMBER OF ORGANIZATIONALAND RESOURCE ACCOUNTS

CURRENT STORAGEAMOUNT/MAILBOX SIZE?

31

3. Approximately how many users on NIPRNET (per location)?3233

LOCATION NUMBEROF

USERS

CURRENTSTORAGE

AMOUNT/MAILBOXSIZE?

IDENTIFYPURPOSE

OF ALLPUBLICFOLDERS

DEFINE PUBLICFOLDER

CAPACITY/USAGE

IDENTIFYYOUR

SPECIALINTERESTCUSTOMERS

34

4. Approximately how many organizational and resource mailboxes on NIPRNET (per35location)?36

37LOCATION NUMBER OF ORGANIZATIONAL

AND RESOURCE ACCOUNTSCURRENT STORAGEAMOUNT/MAILBOX SIZE?

38

39

40


24/42



A-3

41

5. Identify all special interest customers. SES/General Officers may require a separate42storage bin for migration. Identify customized calendar sync and allowed capacities that43may affect migration.44

45SES/GENERAL OFFICERS ANDLOCATION

IDENTIFYCUSTOMIZEDCALENDAR SYNC

ALLOWED CAPACITIES

46

6. Blackberry (N) and SME PED (S) and other special interest users (as necessary,47

begin creating separate storage bin for them or identify storage requirements).4849LOCATION IDENTIFY

ALL SPECIALINTERESTCUSTOMERS

DO YOU HAVEANY RELUSERS?

DO YOU HAVEA FAX OROTHERGATEWAYSERVICES?

IDENTIFY ALLEXCHANGE-DEPENDENTAPPLICATIONS

50515253

INFORMATION: CONCURRENCE BY THE MIGRATION TEAM WITH THE CONTENTS54BELOW IS REQUIRED BEFORE THE INSTALLATIONS MIGRATION CAN BE EXECUTED55(DURING THE ON-SITE INTEGRATION VISIT).56

57

1. Introduction. Number of Exchange organizations on the post/installation and their58names:59

2. Do these organizations have their own TLOU?60

3. Are these organizations in an approved CONUS Domain and Migration Plan for61collapsing organizations into single instance?62

A. Remote satellite locations63

B. Current OWA requirements64

C. Current Blackberry requirements65

D. Email-enabled applications66

E. Other service requirements67

F. Public folders used68

G. Unique ports or protocols required69


25/42



A-4

H. Potential issues & solutions: list any migration or O&M issues.70

4. Storage Limitations/Rules.71

A. OWA requirements72

B. Email-enabled application requirements (please provide specifics: e.g., version73number#)74

C. Blackberry requirements (please provide specifics: e.g., version number)75

D. Other service requirements (please provide specifics: e.g., version number#)76

E. Remote satellite locations77

F. Encrypted email used78

G. Public folders used79

H. Unique ports or protocols required80I. Planned network changes: None81

J. Administrative group structure. (Note: one AG per site. TNOSC will name the82AG Law Naming Conventions.)83

(1) Exchange administrators84

(2) Exchange view-only administrators (potential issues & solutions)85

86

5. Migration Plan TBD*87

A. Preliminary task: identify pilot migration group.88

B. Secondary task: identify migration groups.896. Resource Plan: TBD*90

7. Migration Execution91

A. Migration steps:92

(1) Configuration of scenarios (migration groups)93

(2) Configuration of migration tool with scenario94

(3) Theater approval to proceed past pilot95

(4) Migration execution and reporting96

B. Time line: Estimated time line per 10,000 users (migration team estimate)97

8. Post-Migration Plan98

A. Purpose: application migration99

B. Activities100

9. Operation and maintenance plan101

A. Purpose: decommissioning inventory and schedule102

B. Activities103

104


26/42



A-5

*ITEMS WITH THE ACRONYM TBD WILL BE COORDINATED AND DETERMINED105

DURING IPRS AND SITE VISITS106107

QUESTIONS, CONCERNS AND COMMENTS108LIST ANY ADDITIONAL QUESTIONS, CONCERNS OR COMMENTS HERE:109

110

1.111112

113

2.114115

116

3.117118

119

4.120121

122

123


27/42


Annex B (Installation Sequence List (ISL) Document Template) to HQDA EXORD,LandWarNet Global Network Enterprise Construct (GNEC) Implementation ArmyMigration to DoD Enterprise Email Services

UNCLASSIFIED//FOR OFFICIAL USE ONLYB-1

The existing Installation Sequence Lists of NIPRNet and SIPRNet site migrations can1be downloaded from the following locations. An Intelink Passport account is required to2

access this area.34

DoD Enterprise Email Document Folder:5https://www.intelink.gov/inteldocs/browse.php?fFolderId=19731 6

7

NIPRNet Schedule:8https://www.intelink.gov/inteldocs/view.php?fDocumentId=370320 9

10

SIPRNet Schedule:11https://www.intelink.gov/inteldocs/view.php?fDocumentId=370321 12

13

Submit recommended changes to these sequence lists using the table format provided14below.15

16

If there are issues that affect migration of facilities or large groups of users,17organizations can identify those blocks of dates during which they cannot accomplish18those migrations below.19

20

21

SITE PRIORITY

22

23

24

25

26

27

28

29

30


28/42


Annex C (Guidance on Reducing Mailbox Sizes) to HQDA EXORD, LandWarNet GlobalNetwork Enterprise Construct (GNEC) Implementation Army Migration to DoDEnterprise Email Services

C-1

1

Consistent with actions described in the basic EXORD, it is necessary to reduce2

Microsoft Exchange server-side email storage to no more than 100MB per user.34

The process used to migrate email from the legacy environment to the DoD Enterprise5Email Service includes copying all email located in the legacy Exchange server across6the wide area network to the new DoD Enterprise Email Exchange server. This process7is most effectively performed with as little mail in the users mailbox as possible.8

9

For users who do not have a need to access their email outside of the office10environment, it is recommended that the users Outlook profile be adjusted to deliver11mail to a local PST file located on the users computer.12

13

For users who utilize mobile messaging clients (e.g., Blackberry), this is not an option14as the Blackberry requires access to the email located on the Exchange server. For15these users, it is recommended that all mail older than two weeks be moved off the16Exchange server and placed into local PST files.17

18

These reductions in local Exchange mailbox sizes will facilitate a smooth transition to19the DoD Enterprise Email Service.20

21

Additional guidance and direction will be developed on a site-by-site basis for users who22cannot decrease their server-side mailbox size (e.g. GO, SES, Commanders,23Directors).24

25NOTE: For all users, email can be moved back into their new email server mailbox26once the migration is complete.27

28

As part of this EXORD, organization POCs must track and report their progress in29reducing mailbox sizes to ARCYBER (ATTN: NETC-CG) in consolidated progress30reports. Mailbox reduction consolidated progress reports will include the number of31users with mailboxes greater than 1GB, between 500MB and 1GB, between 100MB and32500MB, and between 0 and 100MB. This information will be provided by location within33each organization.34

35

For information on how to back up mail to a PST or CD, please see the following article36published by Microsoft: http://support.microsoft.com/kb/287070.37

38

39


29/42

UNCLASSIFIED//FOR OFFICIAL USE ONLYDRAFT V0.93 18 Oct 2010


Copy__of__CopiesHeadquarters, Department of the Army

Pentagon, Washington, DC

HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC)

Implementation Army Migration to DoD Enterprise Email Services

(U//FOUO) References:

a. (U) Memorandum, Chief of Staff of the Army (CSA), Subject: LandWarNet Global Network Enterprise Construct Strategy Implementation, dated 2 March 2009.

b. (U) Memorandum, Army CIO/G-6, Global Network Enterprise Construct Transformation of LandWarNet, dated 24 June 2009.

c. (U) HQDA, Planning Order (PLANORD): LandWarNet Global Network Enterprise

Construct (GNEC) Implementation, ALARACT 292/2009, dated 19 October 2009.

d. (U) Army Enterprise Infrastructure Directory Services Naming Conventions andStandards Version 5.1, dated 1 February 2007.

e. (U) DoD Instruction 8551.1; Ports, Protocols, and Services Management, dated 13August 2004

f. (FOUO) DoD Ports, Protocols, and Services Management (DoD-PPSM) ExceptionManagement Process, dated 22 June 2010.

g. (U) General Order No. 5; Establishment of U.S. Army Network EnterpriseTechnology Command/9th Army Signal Command, dated 13 August 2002.

h. (U) General Order No. 2010-26; Establishment of the United States Army CyberCommand, dated 1 October 2010.

i. (U) Memorandum, Under Secretary of the Army (USA), Subject: Guidance onImplementing Army Efficiency Initiatives, dated 2 September 2010.

1. (U) Situation.

a. (U) The CSA memo, reference a., established the Global Network EnterpriseConstruct (GNEC) as the Armys strategy to transform the LandWarNet (LWN) to anArmy Enterprise framework and established NETCOM/9th Signal Command (Army)(NETCOM/9th SC(A)) as the Army's enterprise network manager for Generating Forcenetworks. The GNEC supports four strategic objectives: 1) enabling warfightingcapabilities through the Network, 2) dramatically improving network defense, 3) realizingefficiencies while improving effectiveness, and 4) ensuring Army interoperability with theDepartment of Defense. Since the publishing the CSA memo, the USA memo,


30/42



2

reference i., directed information technology (IT) efficiencies be obtained to meet costsavings for FYs 2012-16, specifically, the migration to an Enterprise E-mail capability as

well as Army data center consolidations. This EXORD directs Army Enterprise E-mailmigration.

b. (U) The scope of this effort includes all Non-secure (NIPRNET) and Secret(SIPRNET) Internet Protocol Router Networks.

2. (U) Mission. The Army will migrate to the Defense Information Systems Agency(DISA) Enterprise E-mail services no later than (NLT) 1 October 2011providing usersaccess to the Enterprise anytime and from anyplace. End state is when Army CyberCommand (ARCYBER) reports that all Army email services are being provided througha single DoD enterprise-level email service.

3. (U) Execution.

a. (U)Intent. The CSA memo, reference a., provided guidance to transformLandWarNet to a centralized, more secure, operationalized and sustainable networkcapable of supporting an expeditionary Army and increase efficiencies for dailyoperations. To achieve this goal, the Army will establish conditions and processes thatprovide ARCYBER with a better understanding of all Army email requirements andenables their consolidation under a single DoD enterprise-level email service.

b. (U) Concept of Operations. The Army migration to DoD enterprise email

services will be conducted in three phases. Phase 1- Discovery, Phase 2- Planning,and Phase 3- Execution. In accordance with (IAW) the CIO/G-6 Army EnterpriseGuidance Board (EGB) decision in September 2010, these phases may be conducted inparallel.

(1) Phase 1 (Discovery): ARCYBER will conduct Discovery activities thatsupport the transition planning for Enterprise objectives by determining the as-is stateof Army email requirements and current email services. All Army organizations willprovide the required data as specified in Annex A (Migration POC and Services DataCall) to NETCOM/9th SC(A) through ARCYBER NLT 45 days upon receipt of thisEXORD. Data requested, collected, and submitted must be classified no higher than

Unclassified//For Official Use Only (U//FOUO). This phase must be completed by anorganization prior to developing Plan of Action and Milestones (POA&M) in Phase 2.This phase is complete for the Army Enterprise when ARCYBER reports that allorganizations have complied with the data call.

(2) Phase 2 (Planning): ARCYBER in coordination with (ICW) ACOMs,ASCCs and DRUs will conduct enterprise email service migration planning to determinethe commands and units that will be subject to this order, the level of effort for each


31/42



3

organization, and identify any potential resource shortfalls. This includes developing aPOA&M for the respective organizations. Subject organizations will also start

preparation for migration to enterprise email services (e.g. reduce mailbox sizes IAWinstructions listed in Annex C) IAW technical guidance to be published by ARCYBERNLT 15 December 2010. This phase is complete for an organization when the POA&M,including the detailed site migration schedule, has been validated by ARCYBER. Thegoal for completing this phase is NLT 30 days prior to start of Phase 3 (Execution) foreach organization.

(3) Phase 3 (Execution): Under the direction of ARCYBER, all Armyorganizations will transition organic email services to the DoD Enterprise Email ServiceNLT 1 October 2011. HQDA begins implementation effective 1 February 2011, followedby the rest of the Army. A detailed scheduled will be published NLT 90 days after

effective date of this EXORD. Any extensions to complete tasks for migrating emailservices will be requested through Commander, ARCYBER (ATTN: NETC-CG). Thisphase is complete when ARCYBER reports that all Army email services are beingprovided through a single DoD enterprise-level email service.

c. (U) Tasks.

(1) (U) HQDA, G-3/5/7.

(a) Monitor the waiver process and maintain visibility of all submittedPOA&Ms from all organizations to ARCYBER (ATTN: NETC-CG).

(b) Conduct monthly in progress reviews (IPRs) with ARCYBER,CIO/G-6 and NETCOM/9TH SC(A) to ensure army enterprise e-mail requirements andspecifications are being met.

(2) (U) HQDA, CIO/G-6.

(a) ICW HQDA G-3/5/7, ARCYBER, AND NETCOM/9TH SC(A)coordinate all resource issues and/or requirements with the Defense InformationSystems Agency (DISA).

(b) Monitor the waiver process and maintain visibility of all submittedPOA&Ms from Army organizations to ARCYBER NETOPS.

(c) Provide cost recovery schedule 8 to HQDA G-8 PA&E andASA(FM&C) (ABO) by 15 November 2010. Schedule 8 will include all Commandscurrently providing email, establish an Enterprise Email budget line (MDEP MSNS,SAG 432), and provide accountability for projected email efficiency.


32/42



4

(3) (U) ARCYBER

(a) Act as the Army lead for migration planning, develop detailed sitelevel migration schedules and assist sites in the actual migration to the DoD EnterpriseEmail Service.

(b) Review, validate and track submitted POA&Ms from allorganizations.

(c) Review and adjudicate all submitted waiver requests from allorganizations within 14 days of receipt from the requesting organization.

(d) Provide monthly updates to the G-3/5/7 and CIO/G-6 on migration

status, to include POA&M and waiver issues.

(e) Ensure the Army Operations Oversight Board (OOB) schedulesand conducts periodic updates during their scheduled events and assesses operationalimpacts on the enterprise.

(f) Participate in monthly IPRs with all stakeholders to ensurecompletion of tasks and continuity throughout.

(g) Act as the overall technical lead and project manager for themigration to DoD Enterprise E-Mail Services and coordinate unique organization

requirements with CIO/G-6 and DISA.

(h) Develop, maintain content, and provide access to the EnterpriseE-Mail web site(https://www.intelink.gov/inteldocs/browse.php?ffolderid=19731/) throughout the migration process. Users must have an Intelink Passport account toaccess the documentation. Follow the instructions on the initial page if you have notpreviously registered at this site.

(i) Develop and publish enterprise e-mail public folder guidance,client configuration, and implementation guidance NLT 45 days after effective date ofthis EXORD.

(j) ICW CIO/G-6, ARCYBER, and DISA, ensure InformationAssurance (IA) guidance is developed and published.

(k) ICW Army Organizations currently having an Exchange e-mailcapability, develop and publish guidance for the creation of command specificInstallation Sequence Lists (ISLs) to be used throughout the planning and migration
http://../Users/gothermanjr/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/Content.Outlook/RVK2QVTH/(https:/www.intelink.gov/inteldocs/browse.php?ffolderid=19731/)http://../Users/gothermanjr/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/Content.Outlook/RVK2QVTH/(https:/www.intelink.gov/inteldocs/browse.php?ffolderid=19731/)http://../Users/gothermanjr/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/Content.Outlook/RVK2QVTH/(https:/www.intelink.gov/inteldocs/browse.php?ffolderid=19731/)http://../Users/gothermanjr/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/Content.Outlook/RVK2QVTH/(https:/www.intelink.gov/inteldocs/browse.php?ffolderid=19731/)


33/42



5

process. Document template is in Annex B (Installation Sequence List (ISL) DocumentTemplate), and at the Enterprise E-Mail web site listed above.

(l) Evaluate and consolidate NIPRNET and SIPRNET requirements,evaluate applications, and coordinate approval and adoption of those meetingexisting/emerging enterprise criteria.

(m) Participate as a voting member in the review processes forenterprise e-mail application and services through the existing Enterprise ConfigurationManagement and Operations Oversight Board business practices.

(n) Establish Army tactics, techniques and procedures (TTPs) for theArmys responsibilities related to operations and management of the DoD Enterprise

Email Service.

(4) (U) Army Organizations. Subject commands and units determined inPhase 2 of this operation will:

(a) Participate in HQDA and/or ARCYBER working groups asrequired to execute tasks in this EXORD.

(b) Provide a Primary and Alternate POC for this EXORD to theCIO/G-6 and ARCYBER POCs NLT 7 days upon receipt.

(c) Implement and report status of mailbox resizing efforts (Annex C)to ARCYBER (ATTN: NETC-CG) on a weekly basis until in full compliance.

(d) Submit completed Migration Checklist IAW Annex A to ARCYBER(ATTN: NETC-CG) NLT 45 days upon receipt of this EXORD. Once Annex A data issubmitted, no additional changes to mailbox enabled applications and additions of newpublic folders should be made. Any operationally required changes must be reported tothe ARCYBER POC.

(e) Validate or make recommendations for changes to InstallationSequence List (Annex B) to ARCYBER (ATT: NETC-CG) NLT 45 days upon receipt of

this EXORD.

(f) If required, submit waiver requests for extension to task(s) in thisEXORD along with associated POA&M to Commander, ARCYBER (ATTN: NETC-CG)NLT 14 days upon receipt of this order. All requests must clearly describe why theextension is required and why it is in the Armys best interest to grant the extension.


34/42



6

(g) Ensure all organic user (Windows) workstations and laptopsaccessing DoD Enterprise Email are configured within the following requirements: AGM

Windows Vista SP2 (or newer), AGM Office 2007 SP2, AGM Tumbleweed DesktopValidator 4.10, and AGM Activclient 6.2. Failure to meet this requirement will result inthe inability to access the DoD Email Service.

(h) Ensure all organic Microsoft Exchange mailbox servers have arecent backup and have had database maintenance performed within 30 days ofscheduled migration date.

(i) Perform migration of organic mailboxes from existing systems intothe DoD Enterprise Email Service in accordance with established Installation SequenceLists.

d. Coordinating Instructions.

(1) (U) Waiver requests for extensions will be submitted to ARCYBER(ATTN: NETC-CG). The waiver must include an updated POA&M that clearlyarticulates the situation causing the delay, proposed remedial actions, estimatedcompletion date and associated timelines, and a primary and alternate POC (name,phone number and e-mail address).

(2) (U) General guidance necessary for reducing mailbox sizes inpreparation and planning for migration is listed in Annex C (Guidance On Reducing

Mailbox Sizes).

(3) (U) The migration checklist template listed in Annex A (Migration POCand Services Data Call) will be used to ensure readiness prior to migration.

4. (U) Administration and Logistics. NLT 7 days on receipt of this EXORD, all taskedorganizations will acknowledge receipt of this EXORD and provide contact informationof designated O-6 level and Action Officer points of contact to the contacts listed inparagraph 5b.

5. (U) Command and Signal.

a. (U) ARCYBER is the supported command for the purposes of this EXORD.

b. (U) Points of Contact.

(1) (U) G-3/5/7 LWN/BC: Ms. Maria Drew, comm: 703-602-7542,[email protected], and Mr. Michael Dowdy, comm: 703-602-7348,[email protected].


35/42



7

(2) (U) CIO/G-6 AONS: LTC Peter Barclay, comm: 703-602-9520,[email protected], and Mr. Thomas Trucks, comm: 703-806-4224,

[email protected].

(3) (U) ARCYBER: LTC Timothy Chafos, comm: 703-706-1611,[email protected].

(4) (U) NETCOM/9TH SC(A): Mr. Michael Bomba, comm: 520-538-6278,[email protected], and Mr. Raymond Turcotte, comm: 520-538-3733,[email protected].

(5) (U) Strategic communications for this initiative is the responsibility of theCommander, ARCYBER.

(6) (U) DIRLAUTH with ARCYBER is authorized.

ACKNOWLEDGE: GEORGE W. CASEY, JR.General, United States Army

OFFICIAL Chief of Staff

DANIEL P. BOLGERLieutenant General, GSDeputy Chief of Staff, G-3/5/7

DISTRIBUTION:Principal Officials of Headquarters, Department of the ArmyCommander

U.S. Army Forces CommandU.S. Army Training and Doctrine Command

U.S. Army Materiel CommandU.S. Army EuropeU.S. Army CentralU.S. Army NorthU.S. Army SouthU.S. Army PacificU.S. Army Special Operations CommandMilitary Surface Deployment and Distribution Command


36/42



8

U.S. Army Space and Missile Defense Command/Army Strategic CommandEighth U.S. Army

U.S. Army Network Enterprise Technology Command/9th Signal Command (Army)U.S. Army Medical CommandU.S. Army Intelligence and Security CommandU.S. Army Criminal Investigation CommandU.S. Army Corps of EngineersU.S. Army Military District of WashingtonU.S. Army Test and Evaluation CommandU.S. Army Reserve CommandU.S. Army Installation Management Command

Superintendent, United States Military AcademyDirector, U.S. Army Acquisition Support Center

U.S. Army Accessions CommandDeputy Under Secretary of the Army (Business Transformation)Director, Small and Disadvantaged Business UtilizationDirector, Enterprise Task Force


37/42



UNCLASSIFIED//FOR OFFICIAL USE ONLYA-1

NO INTERNET PROTOCOL OR DERIVATIVE CLASSIFICATION INFORMATION IS

TO BE PROVIDED

ACTION: Complete information below. List Primary (P) and Alternate (A) POCs foryour organization, theater operations, and for each NEC-like facility.

ORGANIZATION NAME: ___________________________POINTS OF CONTACT FOR ENTERPRISE EMAIL:

POC NAME PHONE AKO EMAIL

ORGANIZATION (P)ORGANIZATION (A)

THEATER (P)

THEATER (A)

NEC [NAME] (P)

NEC [NAME] (A)

IMPORTANT NOTICE: REPEAT NEC AND THEATER ROWS AS NECESSARY.

UNIQUE P RODUCTS AND SERVICES :

Identify any applications (include manufacturer and version number) or services thatprovide unique capabilities that may affect transition to an Enterprise E-Mail Service.

SITE ACCESS INFORMATION. Please provide the POC (Security Managers) TOobtain access to your installations, facilities, and server room facilities (each, asnecessary):

LOCATION NAME EMAIL PHONE NUMBER

(P)(A)


38/42



A-2

EMAIL BASELINE CHECKLIST

1. Approximately how many users on SIPRNET (per location)?

LOCATION CURRENTSTORAGEAMOUNT/MAILBOXSIZE?

DO YOU HAVEANY PUBLICFOLDERS?

TOTALAMOUNT OFDATA IN THEPUBLICFOLDERS

IDENTIFY ALLSPECIALINTERESTCUSTOMERS

2. Approximately how many users on NIPRNET (per location)?

LOCATION CURRENTSTORAGEAMOUNT/MAILBOXSIZE?

IDENTIFYPURPOSE ALLPUBLIC FOLDERS

DEFINE PUBLICFOLDERCAPACITY/USAGE

IDENTIFY YOURSPECIALINTERESTCUSTOMERS

3. Identify all special interest customers, SES/GENERAL OFFICERS- may requiremoving to separate storage bin for migration. Identify customized calendar sync,allowed capacities that may affect migration.

SES/GENERAL OFFICERS ANDLOCATION

IDENTIFYCUSTOMIZEDCALENDAR SYNC

ALLOWED CAPACITIES

4. Blackberry (N) and SME PED (S) and other special interest users (as necessary,begin creating separate storage bin for them or identify storage requirements).

LOCATION IDENTIFYALL SPECIALINTERESTCUSTOMERS

DO YOU HAVEANY RELUSERS?

DO YOU HAVEA FAX OTHERGATEWAYSERVICES?

IDENTIFY ALLEXCHANGEDEPENDENTAPPLICATIONS


39/42



A-3

INFORMATION: CONCURRENCE BY THE MIGRATION TEAM WITH THE CONTENTS

BELOW IS REQUIRED BEFORE THE INSTALLATIONS MIGRATION CAN BE EXECUTED(DURING THE ON-SITE INTEGRATION VISIT).

1. Introduction. Number Of Exchange Organizations on the post/installation and theirnames:

2. Do these organizations have their own TLOU?

3. Are these organizations in an approved CONUS Domain And Migration Plan forcollapsing organizations into single instance:

A. Remote satellite locations.

B. Current OWA requirements.

C. Current Blackberry requirements.D. Email-enabled applications

E. Other service requirements.

F. Public folders used:

G. Unique ports or protocols required.

H. Potential issues & solutions: (list any migration or O&M issues)

4. Storage Limitations/Rules:

A. OWA Requirements:

B. Email-enabled application requirements (Please provide specifics: e.g. version

#):C. Blackberry requirements (Please provide specifics: e.g. version #):

D. Other Service requirements (Please provide specifics: e.g. version #):

E. Remote satellite locations:

F. Encrypted email Used:

G. Public folders used:

H. Unique ports or protocols required:

I. Planned network changes: None

J. Administrative group structure (Note: One AG Per Site. TNOSC will name the AGLaw Naming Conventions)

(1) Exchange administrators.

(2) Exchange view-only administrators (potential issues & solutions):

5. Migration Plan TBD*

A. Preliminary tasks-identify pilot migration group

B. Secondary task- identify migration groups


40/42



A-4

6. Resource Plan: TBD*

7. Migration Execution

A. Migration steps:

(1) Configuration of scenarios (migration groups)

(2) Configuration of migration tool with scenario

(3) Theater approval to proceed past pilot

(4) Migration executing and reporting

B. Timeline: Estimated timeline per 10,000 Users (migration team estimate)

8. Post Migration Plan

A. Purpose: application migration

B. Activities:9. Operations and maintenance plan

A. Purpose: decommissioning inventory and schedule

B. Activities:

*ITEMS WITH THE ACRONYM TBD WILL BE COORDINATED AND DETERMINED

DURING IPRS AND SITE VISITS

QUESTIONS, CONCERNS AND COMMENTSLIST ANY ADDITIONAL QUESTIONS, CONCERNS, OR COMMENTS HERE:

1.

2.

3.

4.


41/42


Annex B (Installation Sequence List (ISL) Document Template) to HQDA EXORD,LandWarNet Global Network Enterprise Construct (GNEC) Implementation ArmyMigration to DoD Enterprise Email Services

UNCLASSIFIED//FOR OFFICIAL USE ONLYB-1

The existing Installation Sequence Lists of NIPRNet and SIPRNet site migrations canbe downloaded from the following location. An Intelink Passport account is required to

access this area.

DoD Enterprise Email Document Folder:https://www.intelink.gov/inteldocs/browse.php?fFolderId=19731

NIPRNet Schedule:https://www.intelink.gov/inteldocs/view.php?fDocumentId=370320

SIPRNet Schedule:https://www.intelink.gov/inteldocs/view.php?fDocumentId=370321

Recommended changes to these sequence lists should be submitted using the tableformat provided below.

If there are issues that affect migration of facilities or large groups of users, this iswhere organizations can identify these blocks of dates where they cannot accomplishthose migrations.

SITE PRIORITY


42/42


Annex C (Guidance on Reducing Mailbox Sizes) to HQDA EXORD, LandWarNet GlobalNetwork Enterprise Construct (GNEC) Implementation Army Migration to DoDEnterprise Email Services

Consistent with actions described and called out in the basic EXORD, it is necessary to

reduce Microsoft Exchange server side email storage to no more than 100MB per user.

The process used to migrate email from the legacy environment to the DoD EnterpriseEmail Service includes copying all email located in the legacy Exchange server acrossthe wide area network to the new DoD Enterprise Email Exchange server. This processis most effectively performed with as little mail in the users mailbox as possible.

For users that do not have a need to access their email outside of the officeenvironment, it is recommended the users Outlook profile be adjusted to deliver theirmail to a local PST file located on the users computer.

For users that utilize mobile messaging clients (e.g. Blackberry), this is not an option asthe Blackberry requires access to the email located on the Exchange server. For theseusers, it is recommended that all mail older than 2 weeks be moved off the Exchangeserver and placed into local PST files.

These reductions in local Exchange mailbox sizes will facilitate a smooth transition tothe DoD Enterprise Email Service.

Additional guidance and direction for users who cannot decrease their server sidemailbox size (e.g. GO, SES, Commanders, Directors) will be developed on a site-by-sitebasis.

NOTE: For all users, email can be moved back into their new email server mailboxonce the migration is complete.

As a part of this FRAGO, Theater POCs must track and report their progress regardingthe reduction of mailbox sizes and provide the NETCOM/9TH SC(A), POC withconsolidated progress reports.

For information on how to backup mail to a PST or CD, please see the following articlepublished by Microsoft for reference and implementation instructions:http://support.microsoft.com/kb/287070 .

Documents

Responsive Document - CREW: Army Corps of Engineers: Regarding Record Management and Cloud Computing: 4/26/2012 - HQDA Pages - Binder