nara tempest

8/3/2019 Nara Tempest

1/101

- , ^ ^ . - " - if.-S- ^ - K S R E^ ' * * * . ^ - - S S S j ? * t j ' ^ ' H S t . ^ '^^i?^!-^ r t"qy-^^r^#'^' i-vfpwg^'^

Nat ional A rch ive s and Records A dm in istrat ion(NARA)Electronic Records Archives (ERA)Facil i t ies PlanCDRLS

May 13, 2005Status: Final

Document Number: NARA -2005-0102Thomas S. Campbell. NARA CO, 301-837-1987Thomas McAndrew, NARA COR, 301-837-1955

National Archives and Records Adm inistration (NARA)8601 Adelphi RoadCollege Park, MD 20740-6001

L O C K M e S O m i A B T i HILockheed Martin Transportation and Security Solutions7615 Ora Glen DriveGreenbelt, MD 20707

Stephen A. Dickison, LMTSS Contract Administrator301-470-4930Marking of Electronic Records Archive (ERA) Deliverable Information. Unless

Otherwise specified or waived by the Contracting Officer, this ERA contractinformation is considered Source Selection Information - See FAR 2.101 and3.104. Use, reproduction, distribution, disclosure or marking of informationcontained herein including technical data is not authorized except by theContracting Off icer in accordance with FAR (SubParts 3.104-4, 27.404(h),Contract Clause D2 (Marking of Contractor Reports), and Section I ContractClause 52.227-14 (Rights in Data).Contract Number: NAM A-04-C-0007


2/101

m^--


3/101

( ^ r F-j,-KL' ^ * - - - - -Te

Contract Number: NAMA-04-C-0007

This page intentionally left blank.

Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005L O C K H B e O M A f t r I N ^


4/101

L - i r i " - T*^ ^V ' IH Ki i ^ " ^ l ^ ^ ' - - = ? ^ " i ^ - ^ j p w ^ T f ^ j ^ j ^ ^"Co ntrac t Nu mb er: NAMA-04-C-0007

Trademark NoticeCompany, product, and service names that appear in this document may be t rademarks or servicemarks of various companies other than Lockheed Martin Transportation and Security Solutions.Change HistoryTable 1 - Change HistoryChange Contact^ H I H H I i ^ ^ ^ ^ ^ H^ ^ ^ ^ ^ ^ ^ ^ | H | H

DateApril 1,2005May 13, 2005

Summary of ChangeInitial IssueSubmittal of Final

Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005L O C K M B S O M A tt T I < ^ ^


5/101

' ^^* J* , " 3*'""'-'^~ < -; - :rr>e^ ^ .i ' 5 ' ' ^ ^ ' ' < 55a^ ^r'^^'~-ff-- --??



Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 ivI o c tf H B B O MA tt r I fi Cf^


6/101

- iwfW^ 'B !? W5lBPT " ' 'T ' " jw p , . j i i i i i i i p p i p B ^ m i P P '

Co ntrac t Num ber: NAMA-04-C-0007

PrefaceThis document was prepared by Lockheed Martin Transportation and Security Solutions (LMTSS) forthe National Archives and Records Administration (NARA) Electronic Records Archives Program Officeper the Electronic Records Archives (ERA) Performance Work Statement (PWS) dated June 9, 2004.It conforms to Data Item D escription (DID) 3.3 specified in the Lockheed Martin ERA P roposal,Appendix B Contract Data Requirements List.DID traceabil ity is docum ented in Table 2 - ERA DID Traceabil ity Matrix and PW S com pliance isdocumented in Table 3 - PW S C ompliance Matrix.Table 2 - ERA DID Traceabil ity MatrixPara No.122.12.233.13.2

DID Paragraph Ti t leIntroductionDevelopment InfrastructureProcessTimelineOperational FacilitiesProcessTimeline

Document Sect ion15453,4,544

Table 3 - PW S Compliance M atrixPara No.5500

PWS Paragraph T i t leFacility Build Out

Document Sec t ionEntire Document

CDRL Number: 5May 13, 2005Source Selection InformationFacilities Plan See FAR 2.101 and 3.10

l O C K M B B t * M A t t T l ^


7/101

. I f H P ' ^


8/101

- - 5 g E ^ ' -Tr- - * " " " ^ 7 " ^ p p ' - i f p s ^ -

Co ntract Num ber: NAMA-04-C-0007


Source S election Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005L O C K M M e O M A

VIt t T I H ^ ^ ^


9/101

' ' ' \ ' A* -^ s=-^^(- 5 - ji f - -; .- ,,.r,,-, i '* y*-sy~

C o n t r a c t N u m b e r : N A M A - 0 4 - C -0 0 0 7

TABLE OF CONTENTS1. INTRODUCTION 11.1 Purpose 11.2 Scope 11.3 Document Organization 11.4 Intended Aud ience 21.5 Referenced Docum ents 21.5.1 Standards 21.5.2 NARA Docu ments 21.5.3 Lockheed Martin Tea m Docum ents 21.5.4 Other Referenced Docum ents 32. ERA ARCHITECTUAL OV ERVIEW 52.1 ERA System Functional Architecture 52.2 ERA Service Oriented Architecture 72.3 ERA System Physical Architecture 82.4 End User Operations 93. FACILITIES MANAG EMENT AND INFRASTRUCTURE 113.1 Facilities Manage ment 113.2 Roles and Responsibilities of Facilities Personnel 143.3 Risk Managem ent Process 183.4 Reporting and Metrics 203.4.1 Program Man agem ent Reviews 213.5 Number and location of ERA Facilities 213.6 NARA Provided Facilities Constraints and Assum ptions 223.7 Facility Criteria 233.7.1 Functional 233.7.2 Data Center 25

3.7.3 Security 263.8 Rep resentative Facility Layout 283.8.1 Facility 1 -Arch ives I I 293.8.2 Facility 2-Irving, TX 323.8.3 Facility 3-St Louis. MO 344. FACILITIES INSTALLAT ION AN D CERTIFICATION PROCESSES 374.1 Operational Facilities Tim eline 384.2 Facilities Proce sses 404.3 Initial Facility Installation 404.3.1 Project Planning and Control Process 414.3.2 Facility Selection Process 444.3.3 Facility Build Out Proc ess 474.3.4 Deploy and Configure the Facility 504.4 Manage Facility Maintenance and Support Process 514.5 Current Facility Retrofit and Expansion 515. PROPOSED FACILITIES 535.1 Lockheed Martin Team Developm ent and Test Facility 535.1.1 Disaster Recovery Provisions 545.2 ERA Propos ed Facilities 54

Source Se lect ion In format ion - See FAR 2.101 and 3 .10CDRL Number : 5 -Faci l i t ies PlanMay 13, 2005 viL O C K H m e O M A R T I N - ^


10/101

- r :!!, s r " ^ ' w j g s w " " " ' - - " -" " " ' ' ^ - ' " " ' " -^T3i>g ii ^ ;i .g j |i jBB ii ^. !L H . i i i , j. . iU l i ia ^ j ui i i iJ l ! Ii: .-,,

ti^jf^EMIP Co ntrac t Nu mb er: NAMA-04-C-00075.2.1 Facility 1 Archives II 555.2.2 Facility 2 Irving, TX 555.2.3 Facility 3 Saint Louis MO 575.2.4 Next Steps for the ERA Facilities 59

6. FACILITY SPECIFIC FRAMEWORK 61LIST OF ABBREV IATIONS 63

Source Selection Information - See FAR 2.101 and 3.10CDRL Num ber: 5 - Facil it ies PlanMay 13, 2005 viiiL O C K H e e O M A I t T f f i ^ ^ J K


11/101

C o n t r a c t N u m b e r : N A M A - 0 4 -C - 0 0 0 7

LIST OF FIGURESFigure 1 - ERA System Functional Architecture - Instance 6Figure 2 - ERA Facility Locations 8Figure 3 - Deployment and Operations & Support Organization 12Figure 4 - ERA design relationship to Facilities and Operations 14Figure 5 - ERA Risk Man agem ent Process 19Figure 6 - Facility 1 Representative Facility Layout 30Figure 7 - Facility 2 Representation Facility Layout 33Figure 8 - Facility 3 Representative Facility Layout 35Figure 9 - Increment 1 Timeline 39Figure 10 - Increment 2 Tim eline 39Figure 11 ERA Developm ent and Test Facility Location 54Figure 12 - Facility 1 Archive s II Facility 55Figure 13- Fa cili ty 2 Irving, TX 56Figure 14-F acili ty 2 Floor Layout 56Figure 15 Facility 3 Saint Louis, MO 58

Source Se lect ion In format ion - See FAR 2.101 and 3 .10CD RL Num ber: 5 - Fac i l i ties P lanMa y 13, 200 5 ixk O C K H S E O M A B T T W ^


12/101

^ ^ , ^ 'W^ ^^- ^ '~ 3 r^- - ; -r - ; a B 3 P ^ W ^ ' ^ ^ 5 7 -^ - ^''^ -r3i



Source S election Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005L O C t t H B B O M A B T I f i C f


13/101

' a F ^ * ^ T i . - ^ i K - i i B 5 r , ^ i ' f . % - 7 i l ^ l H ! j ! ^ ^ i T 5 ^ 5 | ^ ^ ^ t i y j i i ^ ^ ^ g j l l J .1 PR , .. 5 ,, ,, -

C o n t r a c t N u m b e r : N A M A - 0 4 - C -0 0 0 7

LIST OF TABLESTable 1 -Ch ang e History i iiTable 2 - ERA DID Traceab ility Matrix vTable 3 - PWS Compliance Matrix vTable 4 - Sample ERA System Workbe nches 9Table 5 - Roles and Respons ibilities 15Table 6 - Functional Criteria 23Table 7 - Data Center Criteria 25Table 8 - Security Criteria 27Table 9 - Lockheed Martin Project Planning and Control Activities 41Table 10 - NARA Project Planning and Control Responsibilities 43Table 11 -L oc kh ee d Martin Facili ty Selection Activities 45Table 12 - NARA Facility Selection Responsibilities 47Table 13 - Lockheed Martin Facility Build Out Activities 48Table 14 - NARA Facility Build Out Responsibilities 50Table 15 - List of Abbreviations 63

Source Se lect ion In format ion - See FAR 2.101 and 3 .10CD RL Num ber: 5 - Fac i l i ties P lanMay 13, 2005l O C K H S M O M A B T

XI


14/101

f f


15/101



Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 20051 0 C J f r C E 0 M A B T

XII


16/101


1. INTRODUCTION1.1 PurposeThe purpose of the Facilities Plan is to present the Lockheed Martin Team (LM Team) approach tocreating, expanding, or retrofitting an ERA facility from facility selection through facility certification andaccreditation. The plan provides the operational framework to satisfy ERA facility requirements withindustry best practices tailored for the specific needs of the ERA Program.1.2 ScopeThe scope of the Facilities Plan is to present: ERA Architectural Overview and its implications for facilities Organizational view of the facilities and operations team ERA facility selections and criteria ERA representative view and design rational Process to select, insta ll, expand, retrofit, and maintain facilities Proposed facility informationThis initial submission of the facilities plan will also present the timeline for the installation of theLockheed Martin facilities. The current approach to ERA consists of three physical facilities, one atArchives II in College Park, MD (Increment 1) that will house all data classifications; one in middleAmerica that will also house all data classifications (Increment 2); and the third at a contractorowned/operated facility in the Southwest (Increment 1) that will store and processUnclassified/Sensitive but Unclassified (U/SBU) data.This plan is a living document that will be updated over the life of the contract to reflect all changes toERA facilities. Changes will be driven by numerous factors such as facility expans ion, retrofit, or a newfacility to be installed to address new business requirements, significant increase in holdings, andadvances in technology. Some additional examples of triggers are: technology refresh, increasedvolumes of ERA holdings, and new ERA business requirements.1.3 Docum ent Org aniza t ionThe Facilities Plan is organized in the following sections: Section 1: IntroductionDefines the purpose, scope, Lockheed Martin Team organization, and referenced documents forthe facilities plan Section 2: ERA Arch itectural OverviewProvides the context of the overall Lockheed Martin Team solution that the initial facilities will besupporting Section 3: Facilities Management and Infrastructure

Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005L O C K M B B D M A B T I n ^ ^ ^


17/101

Contrac t Num ber: NAMA-04-C-0007

This section provides facility organizational structure and the roles and responsibilities of the teamas well as the requirements, criteria and a representative design needed to select the threeproposed facilities. Section 4: Facilities Installation and Certification Processes

Presents all of the processes to install, expand, or retrofit a facility to include step deliverables, stepfrequency and duration as well as a view of NARA's role in the activities. Section 5: Proposed facilitiesPresents information about the three proposed operational facilities and the development facility. Section 6: Facility specific frameworkCaptures and organizes future facility specific project work to install, retrofit, and maintain the ERAfacilities.1.4 Intended Au die nc eThe intended audience is the ERA Program Management office (PMO) and designated NARApersonnel involved in the facility and facility physical security. The document is also intended forLockheed Martin Team members involved in creating the ERA solution.1.5 Referenced Do cum ents1.5.1 Standards

National Industry Security Program Operating Manual (NISPOM), dated January 1995 Director Central Intelligence Directives (DCID) Telecommunications Electronics Material Protected from Emanating Spurious Transmissions

(TEMPEST) recommendations1.5.2 NARA Do cum ents

ERA Requirements Document (RD), NARA ERA Request for Proposal, Section J2, Amendment001, December 24, 2003 ERA Use Case Document (UCD v2.2), June 18, 2004 NARA Enterprise Architecture Overview (Version 3.2), September 13, 2004

1.5.3 Loc khe ed IVIartin Team D ocu m ents Lockheed Martin Appendix B (CDRL) to the ERA Solicitation No. NAMA-03-R-0018 CDRL 3 - System Architecture and Design Document, Planned for submission April 11, 2005 CDRL 7 - Operations and Support Plan, Planned for subm ission April 11, 2005 CDRL 9 - Risk Management Plan, dated February 25, 2005

Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 2L O C K H B B D M A B T I f l C T


18/101

^ B = r r ] t ^ ^ ! > j ? B i B K ! ^ g m ~ - ' r , , , ^ s ,


CDRL 11 - Security P lan, dated March 30, 2005CDRL 12 - Certification and Accreditation (C&A) Plan, Planned for submission April 21, 2005CDRL 13 - Continuity of Operations Plan, dated March 15, 2005CDRL 16 - Updated Cost Price, Planned for submission June 1, 2005CDRL 18 - Monthly Status ReportsCDRL 22 - Cost Performance ReportCDRL 26 - Earned V alue Management DataCDRL L39 - ERA System Concept of Operations (CONOPS), P lanned for Re-submission April13,2005CDRL L31 - Master Test Plan, Planned for submission April 20, 2005CDRL 35 - Program Management Plan NARA-2004-001, dated October 1, 2004CDRL L41 - Training MaterialsCDRL L44 - ERA Commercial Off the Shelf (COTS) Inventory DatabaseCDRL L55 - System Administrator Guide

1.5.4 Other Referenced Docu me nts Service Component-Based Architectures, V ersion 2.0, June 2004

Source S election Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005L O C K M M E O M A B T T W ^


19/101

- ' T J / -f"-"" i t . - - ^ s a t * - -~JWT - -^^ Ji! .w ^|y -g" ,t



Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005L O C K H M M D M A B TJin^


20/101


21/101

j T , t ^ ,~ - ^ ! { - . ' - J P f ^ ^ K ^ - ' ^ - ' -s ^ r . -

' ^ ' - T ' ^ ^ ^ T T ; ? ' "s^pWig?


2. ERA ARCHITECTUAL OVERVIEWNARA is responsible to the American people as the custodian of a diverse and ever expanding array ofevidence of the American culture and heritage, and of the actions taken by public servants on behalf ofthe American citizens. The core m ission of NARA is that this essential evidence must be identified,preserved, and made available to the appropriate individuals for as long as these authentic records arerequiredregardless of their original form (physical and electronic).The creation and use of an unprecedented and increasing volume of Federal electronic recordsin awide variety of formats, using evolving technologiesposes the fundamental problem that the ERASystem must solve. The ERA S ystem w ill be a comprehensive, systematic, and dynamic means forpreserving virtually any kind of electronic record, free from dependence on any specific hardware orsoftware. The ERA System, when operational, will simplify the means and m echanisms for NARA andNARA's customers to preserve and retrieve the appropriate records while not putting an undue burdenon the Federal Agencies or any other consumer or producer of electronic records.In essence NARA's vision is that the ERA System will: Authentically preserve and provide access to any kind of electronic record, free fromdependency on any specific hardware or software, enabling NARA to carry out its mission nowand into the future;

Address the needs of a large, diverse stakeholder community, while accommodating rapidlychanging technology; Be flexible, scaleable, and extensible to accommodate the ever changing policy, functionality,and technology infusion that will be required of such a system; and Have the capability to be either partially or fully deployed at locations across the United States,such as the National Archives in the Washington area and regional facilities, the PresidentialLibraries and the Federal Record Centers.

The following sections briefly introduce the ERA system level functional architecture, the physical ERAarchitecture, and the user classes and operational aspects of the ERA S ystem to provide a baselinecontext of the ERA System.2.1 ERA System Fun ct ion al Arc h i tec tureFigure 1 illustrates the ERA System functional architecture of an ERA Instance. An ERA Instance is ascalable and configurable set of hardware and software that is deployed at a physical facility thatprovides the business services and functionality necessary to operate an electronic archive. EachERA Instance belongs to a Federation that contains multiple Instances. Instances grouped intoFederation share archive information at the same classification level.The ERA functional architecture shows the relationship between the set of system-level servicepackages necessary to operate an Instance as well as the infrastructure to interface to a suite ofexternal systems. The main services and functions that ERA provides as well as a brief description ofthese system-level services inside an ERA Instance are illustrated below:

Source Selection InformationCDRL Number: 5 - Facilities PlanMay 13, 2005See FAR 2.101 and 3.10

L O C K H M M O M A B r i H ^


22/101


23/101

" " r s T l ' ' ^ ' - T ' 7 ' ' ; w ^ j ' - w 7 5 ^ p p p ^ R ^ T 5 ) ^ P 3 i ^ ! ( P ^ " " ' ^^1^~ '^^~ ' -3 r>" J * : ^ ^ ' i W " ' ^ " ^ ^ i 5 ' " ' ; ^ * ^ iB ' ^ ' " v


Ingest - This system-level service provides the means and m echanisms to receive theelectronic records from the transferring entities and prepares those electronic records forstorage within the ERA System;Records Management - This system-level service provides the services necessary to managethe archival properties and attributes of the electronic records and other assets within the ERASystem as w ell as providing the ability to create and manage new versions of those assets.Records Management includes the management functionality for disposition agreements,disposition instructions, appraisal, transfer agreements, templates, authority sources, recordslife cycle data, descriptions, and arrangements. In addition, access review, redaction, selectedarchival management tasks for non-electronic records, such as the scheduling and appraisalfunctions are also included within the Records Management service.

Figure 1 - ERA System Functional Architecture - Instance^ ERA System Boundary

Inges tW ork i ngS t o rage

InstanceData

Storage

Inges t

Elec t ron icArch ives

Rec o rdsM a n a g e m e n t

Arch iva ls t o rage

Preservat ion

_ r v

-/-v Disseminat ioni l l l

y \ .

Local Serv ices and Cont ro l

Trans fer r ingEnt i t y Sys tems

Interface

Non-Elec t ron icRec o rdsTrack ingSy s t em sInterface

Financ ia lSy s t em sI n t e rnee

User in ter face

Preservation - This system-level service provides the services necessary to manage thepreservation of the electronic records to ensure their continued existence, accessibility, andSource Selection InformationCDRL Number: 5 - Facilities PlanMay 13, 2005

See FAR 2.101 and 3.10

L O C K K I S t S O M A B T I N ^


24/101

s . T ^ - i S ! K= i i i F ' . V I - ! . - . - , - ; ^ : r - : ' s - i " " ? ' ' - - - ^ - - y T - y - - . - ; ^ i , , g , , , , . . ^ - ; . - ^ . . . ^ - , . . . ; , ^ ^ ^ ^ J ! ; y - ! 7 l i j i ; i ) ^


authenticity over time. The Preservation system-level service also provides the managementfunctionality for preservation assessments. Preservation and Service Level plans, authenticityassessment and digital adaptation of electronic records. Archival Storage - This system-level service provides the functionality to abstract the details of

mass storage from the rest of the system. This abstraction allows this service to beappropriately scaled as well as allow new technology to be introduced independent of the othersystem-level services according to NARA's business requirements. Dissemination - This system-level service provides functionality to manage search and accessrequests for assets w ithin the ERA System. Users have the capability to generate searchcriteria, execute searches, view search results and select assets for output or presentation. Thearchitecture provides a framework to enable the use of multiple search engines offering a richchoice of searching capabilities across assets and their contents. Local Services and Control (LS&C) - This system-level service provides all of the functionalinfrastructure for the ERA instance including a user interface portal, user workflow, securityservices, external interfaces to NARA and other Government systems as well as the interfaces

between ERA Instances.The ERA System contains a centralized monitoring and management capability called ERAManagement. The ERA Management hardware and software operate inside a System OperationsCenter (SOC) located at an ERA facility. Each SOC manages one or more Federations of Instancesbased on the classification of the information contained in the Federation. The ERA Managementsystem-level service provides ERA Help Desk functionality, configuration management, andadministration of a Federation of Instances.The ERA system interfaces to various external systems through a series of standard interfaces. Thesestandard interfaces are listed below.

1. Financial Systems;2. Non-Electronic Records Tracking Systems;3. Transferring Entity Systems;4. Help Desk; and5. The ERA System User Interface.

2.2 ERA Service Orien ted Arc h i tec tureThe ERA System will be implemented using a Service Oriented Architecture (SOA) approach. In aSOA, business functionality is delivered by a set of loosely-coupled services that communicate viarequest/response interfaces or by message passing. A mediation layer in the architecture provides thecommunications to the services within an ERA Instance. This mediation layer also communicatesacross ERA Instances (within the same classification level) to other mediation layers for federatedoperations. Business processes are implemented as a composition of services through workfloworchestrations and can evolve as policy changes. Key features of a Service Oriented Architectureinclude:

Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005L O C K M B B O M A B T I N ^


25/101

" - liJ!IJl i.pjKlll l! '.iF^-,*'J'.y.w-


26/101


Each of the Instances participates in a Federation with one or more full or partial Instances at the sameclassification level. While full Instances provide each of the system-level services defined in section2.1, partial Instances that support a subset of these services can be configured without change to thesource release. Each Instance has a Safe-Store location that provides high availability backup to therecords it contains. Instances in the same Federation support load balancing of users and systemprocessing as well as retrieval of records located in another Instance in the Federation.Each one of these facilities will contain one or more Instances, to provide the required functionality forthe end user. Two of the ERA facilities w ill also contain a System Operations Center (SOC). Theprimary SOC will be physically located at the Archives II facility (Increment 1) while the backup SOCwill be physically located at the middle America facility (Increment 2). The physical location of eachSOC will contain the entire associated infrastructure that would be required to manage all of the dataclassifications. While the current deployment plan includes the space for operational personnelperforming SOC services in existing facilities, the operations personnel do not necessarily have to bephysically co-located with the infrastructure. The operations personnel can operate the SOC remotelyprovided they have the appropriate network and security classification infrastructure.ERA supports a broad array of network connectivity. These include the internal ERA Wide AreaNetwork (WAN) and external connections to the world-wlde-web, existing NARANET, and otherGovernment networks. The ERA WAN provides connectivity between Federated Instances.Federations below the TS/SC I level share one WAN while federations at Top Secret/ SensitiveCompartmented Information (TS/SCI) and above share a point-to-point WAN connection. The majorityof consumers and transferring entities will enter the Unclassified/Sensitive but Unclassified (U/SBU)federation of ERA through the world-wide-web. Transferring entities may also employ existingGovernment networks (such as 12) to connect to the ERA system to transfer records. ERA isextensible to support connections to Secret Internet Protocol Router Network (SIPRNET), Non-secureInternet Protocol Router Network (NIPRNET), and Joint Worldwide Intelligence CommunicationsSystem (JWICS) to support classified users access for those who are not on location at ERA facilities.The existing NARANET will provide connectivity to the ERA System for NARA users already attachedto the existing infrastructure as we ll as legacy NARA systems.2.4 End User Op erat ion sThe ERA System operational platform employs a web-based configurable workbench concept. Userslog into the ERA System via a web-based portal, and are presented with a configurable workbench thatis tailored for the kind of work the user chooses and is authorized to perform. Each workbench containsbuilt-in capabilities ("components") to perform specific business processes. These capabilities includeuser-interface components, workflow components, and other services required to complete specificoperational tasks. Table 4 lists the initial workbenches, and the major business processes supportedwithin each workbench. The workbenches and components available to a user will depend on theuser's access privileges. These initial workbenches are based on the NARA Concept of Operationsv4.0 (including the user classes and business process).Table 4 - Sample ERA System W orkbenchesSample WorkbenchesTransferring Entity Business ProcessesMakes or receives records, prepares and transfers them toNARA. This class of users primarily consists of records

Source S election Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005L O C K H B B B M A B T 7 7 f ^


27/101

" Wf:


Sample Workbenches

Appraiser

Records Processor

Preserver

Access Reviewer

Consumer

Administrative User

NARA Manager

Business Processescreators, but the name was chosen to indicate thepredominate interaction with the systemAssesses the records with respect to informational value,artifactual value, evidential value, associational value,administrative va lue, and monetary value and recommendswhich records should be accessioned into NARA's assetsand which should be disposed of by the Transferring Entitywhen no longer needed by the Transferring EntityManages transfers of records, identifies arrangements andcreatesarchival descriptions of records, carries out other processesneeded to ensure the availability of records, and isresponsible for the disposal of temporary recordsPlans the system approach for maintaining the authenticcontext, content, and structure of electronic records over timefor v iewing, use, and downloading. Concisely, the preserverplans processing activities that ensure ability to provide long-term access to electronic records through implementation ofthe Preservation and Service Level PlanReviews security c lassified or othenwise potentially accessrestricted information in order to determine if the informationcan be made available to a consumer, facilitating redaction ofpotentially access restricted information in electronic records.The Access Reviewer reviews records in NARA custody andsets access restrictionsUses the system to search for and access records, to submitFOIA requests, request assistance via mediated searches,communicate with NARA, and invoke system servicesDirectly supports the overall operations and integrity of ERAandits use, and manages such system activities as user accessrights, monitoring system performance, and schedulingreportsReviews system recommendations and makes decisions onwhen and how specific records life-cycle activities occur, andwho w ill perform the work. The manager has ultimateresponsibility for the completion of tasks and the quality of theproducts.

The workbenches use a web-portal framework, which allows new components to be integrated into theoperational platform over time as new business process requirements arise and are met. Thecomponents encapsulate and provide specific features from COTS products, which allow the NARA-defined business proce sses to drive the overall design . This enca psulation con tributes to the key ERArequirement of hardware and software independence.

Source Selection InformationCDRL Number: 5 - Facil it ies P lanMay 13, 2005See FAR 2.101 and 3.10

10L O C K H B B O M A B T t H ^


28/101

ipr^- - - - - - - - '-


29/101

Tjj^m p' -tai i -^sf i :.- -i- i i - ^ ^ - ^ ^ ' i m . ^ : . ;j:^**'if^,


30/101

- *


31/101

^f j i -w^!? "-' wt^^w.^ m" h- 9W?"' " r> S' - f lSi t >^ . ' igfB ^; i ^-< 'T . 5 jp!ni- j


Source Selection Information - See FAR 2.101 and 3.10CDRL Num ber: 5 - Facil it ies PlanMay 13, 2005 12L O C X M B B O M A B r i H ^


32/101

K s,*"'^ - ' ^ w^iK.-'v i' j p i . fl y , ' ; .w > ' j ^" ( l< ' J ^ - ' ^ W ^ I i i M S F f l B ^ I J ; I f - ^ r = ^ ^ ? c^ ~- , r^!W ,v ,


Source S election Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 13L O C t t H B B O M A B T T W ^


33/101

, r= W T > " -- ^ -- '- ~ - y - -- - - < i - . - ! r - ^ , . p g . - .i , . , .^ , ^ ^ - B] 5 | | , S^ , , , r- i ^ - - . 3 5 , ^ 5


Source Selection Information - See FAR 2.101 and 3.10CDRL Num ber: 5 - Facil it ies PlanMay 13, 2005 14L O C t t H B B O M A B T T i r ^


34/101

. P J | l - P | p i l l . " * . ^ W 4 l l l . i U . ^ ' " ^ ^ ^ ' S S ^ ? ^ - V T ^ '


Table 5 - Roles and Responsibilities


35/101

^ ^ ^'


36/101

'v'wr. , ^ , K J W | f ; . R S ' ' i V # , # " ? f l H n i " ; ^ n ^ " "S^fl^"^ i ^ jVTi^^ ! j p r ; ; w;^w^5(?^fs^Br- '^^pF'=.- jwr



37/101

m i ^ ' ' i


38/101

^-^' ' ' sa'^pr-.^TB'^^-a^.^^R-



39/101


40/101

" V vmf-iVjm. n JU rai'M il^i -7r*'9;->t'?,'4'*''.

Con tract Num ber: NAMA-04-C-0007


41/101

" ^ " ^ ' ( * t i " i y . W H f J P ' ^ ' ^ ' ' ^ ' JA ^ H^ F ^ "T'^^^r.,?)3>n f l^r- '5~' ^^^^l^' 'T^'^'r f^~^' ' '^^S" 'T^^! r '- -


Source Selection Information - See FAR 2.101 and 3.10CDRL Num ber: 5 - Facil it ies PlanMay 13, 2005 19L O C K H B B O M A BTTir^


42/101


43/101

-v >.. Ji8'im ^i iiwpii-4is!SJHipn.


3.4.1 Program l\/lanagement ReviewsThe Deployment and Operations Manager will participate in Program Management Reviews. Thesemeetings include: Monthly Status Review Cost Schedule ReviewAt the S ubcontract Program Manager Review, items addressed will include: Subcontract status Subcontract cost and schedule3.5 Num ber and locat io n o f ERA Faci l i t iesThe Lockheed Martin Team presented a Non - CDRL White Paper entitled Optimum ERA FacilityLocation, dated March 11, 2005 that described in detail the process used to determine the number andlocation of facilities described in section 2.3 ERA System Physical Architecture of this document.The following is a summary of that white paper.Three options were considered:1. A total of five (5) ERA processing facilities, three (3) processing U/SBU holdings only and two (2)processing ERA holdings classified as Confidential & /Secret/Top Secret/Sensitive CompartmentedInformation (S/TS/SCI)2. Two facilities that could each accommodate all classification levels of NARA holdings3. A total of three (3) facilities, of which two (2) can process all classifications of holdings and one (1)facility that processes SBU holdings only.Striking the proper balance between cost considerations of the ERA facilities configuration andperformance criteria is the key to establishing value. Accordingly, the ERA facilities white paperseparated cost considerations from all of the other selection criteria used to determine the propernumber of ERA facilities. The first step considered various technical performance and human factors toquantify the three different facility configuration options. That was accomplished by describing eachoption, discussing its relative pros and cons, and applying weighted scoring criteria to technicalproficiency, customer preference, Safe-Store proficiency, and schedule considerations. Option 3scored the highest and is a very balanced option providing solid technical m erits w ith Safe-Store andinter-facility load balancing being major deciding considerations.The selected option provides three (3) facilities, of which two (2) can process all classifications ofholdings and one facility that processes U/SBU holdings only. The Lockheed Martin Team currentlyproposes the following three (3) facilities but will present the final facility selections with CDRL 16,Updated Cost Price: Facility 1 - Archives II in College Park, MD, a NARA facility to be installed during Increment 1 thatwill process at all data classifications Facility 2 - Contractor owned facility that will be leased to NARA located at 1925 John CarpenterFreeway, Suite 425, Irving, TX to be installed in Increment 1 that will process U/SBU data only Facility 3 - A commercial facility that will be leased to NARA located at 210 North Tucker, Suite800, St Louis, MO, to be installed during increment 2 that will process at all data classifications.Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 21

L O C K H B B O M A B T I f i ^ ^ J r "


44/101


The cost reduction implications caused by reducing the number of facilities are dramatic. The mostsignificant savings is realized with the two facility configuration. The cost difference between a two (2)and three (3) facility configuration though tangible, is close enough to merit the 3 facility configurationas the ultimate solution due to active Safe-Store, and inter-facility load balancing advantages.The white paper recommendation was that one of the ERA facilities should be on government ownedor leased space located on the East Coast within easy access of greater Metropolitan DC, but not inthe District. The second and third major ERA facilities should be geographically dispersed so that theyare in areas of the country that have different weather patterns. This classic approach to having datacenters dispersed in different areas of the country is taken because it affords protection againstmultiple facilities being impacted by a single disaster. Since presenting the white paper, facilities havebeen selected in S t. Louis, M O, and Irving, TX based upon consideration of availability and cost of atechnical labor pool, cost of facilities, availability of robust communication networks, and proximity tothe Federal Record Center. NARA named the Archives II facility in College Park, MD as an ERAfacility in guidance that is summarized in the following section:3.6 NARA Provid ed Faci l i t ies Co nstra in ts and As sum pt io nsThe contracting officer, Sylvia E. Edwards, sent a letter on January 5, 2005 that documented FacilitiesConstraints and Assumptions as a change to be incorporated into the National Archives and RecordsAdministration contract number NARA-04-C-0007 for the Electronic Record Archive (ERA) Program.The following is a summary of the guidance provided in that letter: The ERA approach includes active Safe-Store and a group of instances At least one copy of all ERA holdings of electronic records is stored in facilities controlled by NARA For purposes of CDRL 16 "Updated Cost Price" that the NARA controlled Instance will be located atArchives II in College Park, Maryland in Increment 1 The contractor should assume that NARA will incur all build-out and facilities costs for the facility atArchives II The contractors updated proposal should contain projected facility requirements for Archives II (i.e.,estimated power needs, raised floor space, cooling etc.), as we ll as estimated operations personnel(space and fac ility), space, requirements, etc The contractor should include communication costs to Archives II The contractor should include any employee costs (other than space and facilities) for operationalpersonnel that will be stationed at Archives II The contractor shall include in their price all cost for other facilities proposed Geographic separation of at least 100 miles is required for any 2 instances that are Safe-Store ofdata of each other There are no constraints precluding 2 or more instances from occupying the same facility as long

as other constraints are met.The Lockheed Martin Team understands that the ERA Statement of Objectives (SOO) constraints andconcepts s till apply except where overridden by a constraint or assumption presented in the letter.

Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 22L O C K H B B O M A B T i H ^


45/101


46/101


3 .7 Fac i l i t y C r i t e r i aThe Lockheed Martin Te am established facil ity criteria and representative facil ity layouts for all threeERA operational facil it ies to facil itate the selection o f the most a ppropriate facil it ies. The criteria andlayouts were prepared du ring the requiremen ts and early design phase . The criteria and representativefacil ity layouts were then provided to L ockheed Martin Team facil ity specialists who worked w ith realestate brokers to provide potential addresses fo r ERA Facility conside ration. The propose d facil it ieswere chosen from those lists. Section 3.7 d escribes the facility criteria and s ection 3.8 provides therepresentative facil ity layouts used in the facil ity search . Final ERA operationa l facil ity selections will benamed in CDRL 16, Updated Cost P rice, which will also include the finalized criteria and representativefacil ity layouts that will reflect updates base d upon the com pleted System s Architecture a nd Designdocument and ERA equipment Bil l of Materials (BOM).There are three (3) categories of criteria: Section 3.7.1 Functional, supplies criteria required of the facil ity to support the ERA functions to beperformed at that facility Section 3.7.2 Data Center, supplies the technical data center criteria required Section 3.7.3 Sec urity, supplies security criteria in general terms to avoid the need to classify thecriteria and this version of the Facility PlanThe listed criteria is not an absolute check list where one n on-conforma nce would eliminate a facil ityfrom further con sideration. The most obvious exa mple is that a facil ity shou ld not be eliminated fromconsideration if it is not currently an o perating data cen ter. The cost for leasing an existing data centerspace that meets all of the criteria must be balanced against lease plus build out costs for space in afacility that is suitable to support a data center.Accordingly, the following types of facil ities are all legitimate o ptions for c onsidera tion: an existingoperating data center, a closed dow n data center, and a facility that can be mo dified to become a datacenter. All of these options w ould need to undergo som e level of construction to meet the ERA criteriaand representative facil ity layouts presented in 3.8 of this docum ent. Co nstructing a new facility wasnot considered to be a viable option at this time due to cost and schedule constraints.3 . 7 . 1 F u n c t i o n a lThe functional requiremen ts p resented in Table 6 - Functional Criteria provides the context for thespace usage and sepa rate areas/roo ms that will need to exist within the spa ce. These criteria describegeneral function that in m ost cas es app ly to all three facil it ies. An "x" in the column for a particularfacility indicates a function that is required at that particular facility. Specific square footage will beavailable at the completion of design phase an d will be docum ented in the Bil l of M aterial within thecost proposal. Specific criteria that are driven by the handling of ERA holdings with S /TS and TS /SCIclassifications will be listed in section 3.7.3 Security.

Table 6 - Functional CriteriaFun ct ional Cri ter ia I Fac i l i ty 1 | Fa cil i ty 2 | Fa cil i ty 3

Source Selection Information - See FAR 2.101 and 3.10CDRL Num ber: 5 - Facil ities PlanMay 13, 2005 23r I fi \^Jt^O C K H B B O M A B


47/101


48/101


49/101

, , ~ , ^TF- 'T^gs ' ' ' \ f * e^ ' '


Funct ional Cri ter iaSq Ft = tbdWork space for loading media types into drives formoving data files from media into the ERA system w ithincages in the data center.Sq Ft = tbdSpace for a U/SBU SOCSq Ft = tbdSpace for a S/TS SOCSq Ft = tbdSpace for a TS/SCI SOCSq Ft = tbdFreight or other heavy duty elevator service to the floortop accommodate m ovement of computer equipmentincluding tape storage robotic units

Faci l i ty 1X

XXXX

Faci l i ty 2X

X

Faci l i ty 3X

XXXX

3.7.2 Data Ce nte rTable 7 - Data Center Criteria presents the Lockheed Martin Team's data center requirements. Eachdata center requ irement ap plies to all three facil it ies. Data center facil it ies m eeting these criteriaprovide a very stable proc essing en vironment that, combined with the S afe-Store a nd auto fail overarchitecture, wil l meet E RA ava ilability performance requirements. A facil ity m eeting theserequirements provides a h igh level of performance w ithout the significant expen se of duplicating ailelectrical switchgear, Uninterrupted Power Supply (UPS), alternate power generator, and powerdistribution system s.Table 7 - Data Center CriteriaData Center CriteriaDedicated close-control air conditioning with back-upSystem Monitors with remote notificationsFacility access controls a nd su rveil lance systemsFire detection and suppres sionLightening protectionEquipment groundingElectric switch gear and power d istribution units72 hour UPS capa bilitiesPower back-up via standby generator

Faci l i ty 1XXXXXXXXX



Source Selection Information - See FAR 2.101 and 3.10CDRL Num ber: 5 - Facil it ies PlanMay 13, 2005 25L O C K H B B O M A B T I N ^


50/101

-1 ,^j|mpi ^-i^-ffT'cr'- '"^^ -J \ -^ r ip^'-sj^^v ^i f r^-w- ' '^V-~^f^' i


Data Center CriteriaTransient voltage surge protectionFacilities with secure perimeter wallsFacility to withstand 150mile/hr wind loadingFacility power to accomm odate data center functions.Target of 65 watts/SFMust have the abil ity to scale watts /sq ft as needed byfinal BOM and design densitySeparation from hazardous facil it ies, RR yards, fuelstorage, hurricanes and tornado zones, and has goodfacility drainageFacility fre e of hazardous materials and wasteLease entire space .Availability to expand per program planSecured exterior yard spac e, or interior spac e, forcondenser un its, gene rators, transform ers, electrical &mechanical infrastructures sha ll be availablePermitting review and issuing w ithin reasonable timeschedulesUnused telecommu nications fiber (dark fiber) to thefacilityParking providedMultiple power utility sourcesMultiple Telecommunication sources

Faci l i ty 1XXXX

X

XX

X

X

X

XXX

Faci l i ty 2XXXX

X

XX

X

X

X

XXX

Faci l i ty 3XXXX

X

XX

X

X

X

XXX

3.7 .3 Secur i t ySecurity requirements affect all ERA facilities but are particularly important in facilities 1 and 3 whichwill house and process ERA holdings at all levels of classification. ERA facil it ies handling classifiedelectronic records must m eet the DCID requiremen ts for Sensitive C omp artmented Information Facility(SCIF) and collateral materials area construction and TEMPEST recommendations for preventing theintercept of electronic em anations . To a ccurately access a facil ity's abil ity to cos t effectively meet the

Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 26L O C K H B B O M A B T I N J ^ ^ J ^


51/101

.-^-^tj fflniaiTfr- - B - ! | - ' - Y - - " ' / ' W - - i f f i


DCID, NISPOM, and TEMPEST standards, a site survey of the facility must be performed by PhysicalSecurity Subject Matter Expert (PS/SME). However, screening facilities for consideration in the facilityselection process according to the following criteria, will focus site survey resources on those facilitiesthat have a higher likelihood of being selected. Table 8 - Security Criteria presents the securityrequirements the Lockheed Martin Team used to locate the proposed facilities.Table 8 - Security CriteriaSecuri ty Cri ter iaAbility to receive cou rier service of media containingclassified materialSpace for a location to sanitize mediaSpace for a location to destroy mediaSpace for document control to distribute classified mediawithin theclassified Instance a reaSpace must becapable of handling system instances atall security classification levels U/SBU/S /TS/TSS CI canmeet DCID 6/9 and TEMP EST securityrecommendations(Note: this requirement requires a facility visit byIndustrial Security Office to determine)Facility provides or allows 24x7 controlled access viaArmed Guards within the facilityResponse force (facil ity armed guard) capable ofresponding to an alarm within 5 minutesReserve response force a vailable to assist theresponding force (includes local law enforcement orPrivate security force)Facility allows con tinuous ope rating m ode of the datacenter 24x7Raised floor isn't a system requirementHowever if raised floor e xists, it is required to have 1foot or more of observable floors space beneath thefloor. This can be through monitors or by placing thecables or fiber inside a pressure conduit that woulddetect someone tampering with the cables/fibersFacility must provide a SCIF or the ability to build a SCIF

Faci l i ty 1X

XXX

X

X

XX

X

XX

X

Faci l i ty 2

X

X

XX

X

X

Faci l i ty 3X

XXX

X

X

XX

X

XX

XSource Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 27

L O C K H B B O M A B T T T ^


52/101

^ ' ^ ^ ^ i . ^ " i ^ ^^^s :x i . : i


Securi ty Cri ter iato DCID 6/9 StandardsFacility must provide a collateral area or the ability tobuild a collateral area to DCID 6/9 StandardsFacility must provide, or provide the ability to create, afiber pure environment within the S CIF to eliminate theneed for separation from the power runs like a coppercategory 5 cable equipped facil ityConcrete floorsAbo ve the 3' floorMinimum ceil ing height of 9 feetStand alone single tenant facil ity with 100 meters ofobservable space around entire facility perimeterAbil ity to install numerou s s ophisticated lockeddooHrt/ays providing meeting DCID standards betweenClassified areas as illustrated on the logical facilitydrawingAbility to construct physical constraining barriersbetween m ultiple areas of the facil ity such as walls andlocked cages or meshed wire walls.Ability to put line filters on all power lines.

Fac i l i ty 1

XX

XXXXX

X

X

Faci l i ty 2

X

X

X

Faci l i ty 3

XX

XXXXX

X

X

3 .8 R e p re s e n t a t i v e F a c i l i t y L a y o u tThe Lockheed M artin Tea m deve loped a representative facilit ies layout for each of the three proposedfacil it ies. The facil ity layouts were base d upon extensive experience in facil it ies and know ing the USGovernment certif ication and accreditation processes. These represen tative layouts provide the ERAPMO a thorough understanding of ERA requirements and the Lockheed Martin Team's approach tofacilit ies design. During the next phase of the program , the Lockheed Martin Team will select theactual facil it ies for the ERA system . During this phase of the prog ram , the representative facil itylayouts need to be flexible en ough to be implemented in various types of facil ity sce narios, such as:

Standalone single tenant facil ity with perimeter fence W ing of a facil ity A floor within a facil ity with external elevator access

CDRL Number: 5May 13, 2005Source Selection InformationFacilities Plan See FAR 2.101 and 3.10 28

L O C K H B B O M A B T I N ^


53/101

i p | i 4 i i " ;


54/101


3.8.1 Facility 1 - Arch iv es IIERA PMO provided guidance that one of the ERA facilities will be at the NARA Archives II facility. TheLockheed Martin Team has assigned Archives II to be Facility 1. This facility will house Instances at alllevels of classification, the Primary SOC, and the ERA Help Desk. The Archives II facility will provideERA PMO easy access to operations and it provides close proximity to the Lockheed Martin Team.Until the facility in increment 2 is operational, this facility at Archives II w ill house an active or Safe-Store copy of all ERA electronic holdings. After increment 2 is deployed this facility will serve as theSafe-Store for facility 3 classified electronic holdings and one half of facility 2 U/SBU electronicholdings. Easy access for cleared NARA archivists is the reason the Archives II facility will be used asthe ingest facility, and holder of the active copy, for all classified holdings under normal operatingconditionsFigure 6 - Facility 1 Representative Facility Layout shows the representative layout for Archives II. It isreferred to as a representative layout because it a conceptual view of the functions supported by thefacility, not an actual floor pan drawn to scale. The drawing in Figure 6 - Facility 1 RepresentativeFacility Layout illustrates the Facility has 3 major sections: Unclassified surrounding the perimeter ofthe building, SCIF area to handle TS/SCI Instances, and a Collateral area to handle S/TS Instances.The areas are marked for the convenience of the reader and are color coded for the Lockheed MartinTeam facility specialists who use these documents to better understand the facility criteria. Thisrepresentative floor plan will be enhanced to scale and to show common areas such as FacilityManager Office, bathrooms, and break area after the design phase and BOM are completed for useduring the creation of the Cost proposal. Architectural facility drawings will be created after DownSelect.

Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 29L O C K H B B O M A B T I f J P


55/101

T


56/101

" ^ ^ ' --^ ' 'fSM^PU "|^|fl '-ff"^**^a^"'"^^ "^^'gfag^wy^ggy^^-'


Figure 6 - Facility 1 Represe ntative Facil ity LayoutSource Selection InformationCDRL Num ber: 5 - Facil it ies PlanMay 13,2005

See FAR 2.101 and 3.1030

L O C K H B B O M A B T I T T ^


57/101

r ? * ' f ^ l g i ^ J M i # ^ s s ; ^ ^ ^ ' r. ^-^c* , fB^""M(' iows(!e ' . f ^ ^


The Lockheed Martin facility design approach first evaluated the receiving rooms for physical items.The design team categorized two major types of receipts: system equipment and m edia. For systemequipment, the design had to accommodate the arrival of large Information Technology (IT) systemsthat could be inventoried and accounted for quickly, assembled and tested conveniently, then movedinto the operational location for permanent placement. A flow pattern was developed on the left portionof the facility for these tasks. A controlled environment was established to minimize particlecontamination to ensure the longest life for all computing resources. The rece ipt of media can beperformed at assembly area or by the armed guard in the main entry reception a rea. The unclassifledmedia would be opened in the assembly area to control dust and than taken to the appropriate systemequipment for loading. Receipt of classified media would be controlled by a cleared armed guard whowould escort the courier or cleared user to the appropriate classified location.The fioor design had to be convenient for operation and maintenance activities. Our design allocatedall the computing resources close to the receipt and assembly room. This will allow for convenientremoval of components and limit the access for vendors. The components can be installed directly intoposition or removed and brought to a convenient egress door to turn over to the vendor for evacuationback to a higher level of maintenance support. Minimal disruption to the facility was one of the designgoals.Our design also evaluated the fiow of human traffic. All visitors follow sign in procedures at thereception station and are escorted to the armed Guard station. The armed guard will monitor theU/SBU area. The armed guard will also collect electronic devices, inifiate positive control and escortvisitors requiring access to the SCIF and Collateral area. Industrial Security Officers inside the SCIFand Collateral areas will maintain positive control of all visitors and ensure that all access/egress,system use, and document control will conform to DCID and NISPOM standards.Having two cleared armed guards allows for achieving a continuous operation status even when thereis not an Industrial Security Officer or SOC technician present in the SCIF and for coverage at thereception area, and for security coverage when one armed guard is on a roving patrol or break. Acontinuous operation status allows for drywall construction for the SCIF. Internal to the classified areaand the SCI classified area, workstations were located close to their respective SOC providing an extraelement of security through mere presence and proximity. Additionally, the classified sections werecentralized and grouped together to limit the emanation intercept threat. Use of fiber cabling within theclassified areas meets TEMPEST recommendations with the least amount of separation possible. Theclassified workstations w ere grouped together and located on the perimeter of the classified areas toprovide a short inspectable distance for cabling between processing equipment and locked user roomswhich provide a measure of security from emanation intercept. Placing the classified video monitors,which are the greatest source of potential intercept, close together and close to the wall means thatany eavesdropping antennas and systems would have to be able to pickup and sort out whichemanation belonged to which terminal and would have to sort through two layers.Next, all classified equipment was grouped together to keep the number of TEMPEST required devicesto a minimum. The Power D istribufion Units (PDU) that might require in-line power iltersweregrouped close by to minimize the number of exposed lines. The racks were centralized to minimize thenumber of security devices that would be needed to provide encryption or a controlled interface to beable to converge the networks as described by the security decisions.The consideration and use of dry wall to separate the instances of the classified ERA and user roomswas examined closely. Dry wall, while providing a level of comfort for those looking for visual security,

Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilifies PlanMay 13, 2005 31L O C K H B B O M A B T n r ^


58/101

i^ >Tm^~r~ .f, -i-.-'- ; ' " ' " - ' f ! - - 3 - ^ l _ " W l W y ^ i i . . , , _ . , ,,...,,,^^j^p^j5;,,j,,,j;^..gf_^^^^,^^


does pose problems with ventilafion and cooling efficiency. IT systems of this magnitude give offenormous quantities of heat. Heat is detrimental to any computer system and as such, the computersystems must be cooled efficiently. Othenwise, the maintenance problems of the systems would hinderthe ability to meet the required system availability performance goals. The Lockheed Martin Teamapproach is to use heavy duty wire meshed cages around the processing equipment to providefollowing benefits:Improve circulation - Cool air around all heat generating componentsProv ide f lexibi lit y - Should the estimates for fioor space be inaccurate, wire meshed cage walls aremuch easier to relocate or move and they do not produce the dust that is created when dry wall mustbe dismantled and moved. The particle control is much better with a caged environment as well asthermal control.3.8.2 Fac il i ty 2 - Irv ing , TXThe Lockheed Martin Team's approach for Facility 2 is to house 100 percent of all U/SBU data; 50percent active, and 50 percent Safe-Store of facility 1 and facility 3 unclassified data. Facility 1 andfacility 3, which are both government controlled facilities will each provide Safe-Store for the facility 2unclassified data. This configuration meets the requirement to house 100 percent of all electronic ERAholdings on Government controlled space while providing the ability to house significant proportions ofall ERA holdings in a facility that is not constrained by the cost and inflexibility of SCIF construction andphysical access control requirements for classified holdings. This approach provides a cost effectivesolution and the lexibility or facility 2 to be a contractor controlled facility.The following representative design for facility 2 followed the same concepts as facility 1 includingreception of equipment, people and security. The flow of people and ease of access were the driversfor this design.

Source S election Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 32L O C K H B B O M A B T I N < ^ ^


59/101


Figure 7 - Facility 2 Representation Facility LayoutEquipment receipt would be performed in the assembly area. This would provide easy access to theequipment room. The same consideration on the placement of racks and PDUs for the computational

Source S election Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 33L O C K H B B O M A B T I N - &


60/101


equipment was applied as for facility 1. However, since this is an unclassifled facility, there will be noDCID 6/9 facility construction standards for SCIF or classifled collateral areas construction whichallows for optimum space to house the processing and storage devices.The personnel entry would be through the secured area with an armed guard to meet NARA controlledaccess requirements. Our design provides for ERA user workstations at the facility which are in closeproximity to the armed guard desk allowing the armed guard easy access to monitor the users.3.8.3 Fac il i ty 3 - St Lo ui s, MOThe Lockheed Martin Team 's approach to that of facility 3 was similar to facility 1. Facility 3 wouldhouse ERA Instances of all classifications of data. This facility will serve as the S afe-Store for facility 1classified and U/SBU electronic holdings and one half of facility 2 U/SBU electronic holdings. Facility 3will have the capability to ingest and house active classified holdings the same as Archives II if needed.The identical design criteria used for facility 1 was applied to the facility 3 design with the followingpractical differences between the facilities:

Facility 3 provides backup SOC Facility 3 provides backup help desk Facility 3 provides limited number of user workstations

The Lockheed Martin Team's goal was to provide backup capabilifies in facility 3 to protect againstinterruptions in service caused by disaster situations.

Source S election Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 34L O C K H B B O M A B T I B i < ^


61/101

I P P " ^ *


62/101

^ ^sf*^ g ; ^ i r ^ .--;-5JV-^i(.j-y!> ^ 1 ^ ,.


Figure 8 - Facility 3 Representative Facility Layout

Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 35L O C K H B B O M A B T T i r ^


63/101


64/101

. - - w " . ^ - " r - J f ^ l ^ f ^ - B ^ - - " i V i - H f ^ ? - . ^ ' --miS . ^ ^ - T ^ ' -



Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 36L O C K H B B O M A B T H T ^


65/101

r.P--SS:>" TK ..'-wpri : ' IP '7 ;1


4. FACILITIES INSTALLATION AND CERTIFICATION PROCESSESLockheed Martin ERA facilities w ill provide the environment to support the deployment of the ERAsolution and the Lockheed Martin Team. As such the total ERA facilifies environment must provide: Stability to provide a safe effective workplace Reliability to meet availability performance requirements Flexibility to accomm odate the wide array of funcfional requirements Security by meeting physical facility and system regulafions.To ensure that outcome, the Lockheed Martin Team has created an approach for facility installationand certification that is process driven to that includes:

Involvement of the right subject matter experts through an IPT approachIntegration into the overall Lockheed Martin ERA Program Management PlanComprehensive management and control of the processCreation and use of tools to help subcontract vendors perform to expectationEncouragement of NARA active participation In the IPT to gain perspective and guidanceIncorporafion of checkpoints for ERA PMO approval at project milestonesConsideration of facility certificafion and accreditation requirements every day of the projectSecurity authenticating authority pre-approvals of work products at checkpointsAdherence to facility data center criteria that produces a known standard of performanceRisk identification and risk management activifies.The processes described in Section 4 apply to all ERA Operafional Facilifies. The Lockheed MartinTeam Development and Test facility shall adhere to standard Lockheed Martin facility processes forfacility operations and maintenance. Secfion 5.1 Lockheed Martin Team Development and Test Facilityprovides a descripfion of the development and test facility.The Lockheed Martin Team processes to install, deploy, retrofit, and maintain an ERA data center areprovided in secfions 4.3 through 4.5 of this docum ent The core process is described in section 4.3.1,Project Planning and Control Process; 4.3.2 Facility Selection Process; and section 4.3.3 Facility BuildOut Process. The detailed process steps contained In these three secfions encompass the acfivitiesrequired to install and certify an ERA facility that processes holdings of all classification levels. Thisprocess requires 18 months from beginning of requirements gathering through achieving certification.The process and the timeframes for detailed steps is a guideline for the installation of an ERAclassified facility to be used for the installation of any ERA facility at any point is time. The applicationof the general process for the installation of a specific facility will result in a tailored imelinewithin theintegrated schedule. Adjustments can be made to the general installation process. An example of anadjustment is installing a new U/SBU facility is less time consuming that installing a facility to handle allclassification levels.

Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 37L O C K H B B O M A B T I N


66/101


4 . 1 O p e ra t i o n a l F a c i l i t i e s T i m e l i n eThe following timelines for Increm ent 1 displayed inFigure 9 - Increment 1 Timeline, andFigure 10 - Increment 2 Timeline graph ically depict the Lockheed M artin timeframe s for installation ofthe initial three ERA Ope rational Fac il it ies. Each figure refiects the two eleme nts; Process phaserepresented as continuous bars, and significant facility activit ies represented as plot points.Facility 1 represents the total process time of 18 months for a facil ity that processes ERA holdings atall classification levels. Adjustm ents fro m the genera l process timeframe s for a sh orter duration forfacility 2 and facil ity 3 are reflected b ecause the Lockheed Martin Tea m is assuming that the use of thesame General Contractor and SCIF Contractor, thus reducing eliminating the contractor bid processtime for those facil ities. Additionally Facil ity 2 does not process Classified records. The S CIF andCollateral areas will be con structed in increm ent 1 for Facility 1 but a second fit out and certificationtimeframe in increment 2 is needed to coincide with the ERA classified records processing release. It ismore cost effective to construct the S CIF at the same time as the rest of the facil ity. How ever, placingthe actual computer equipm ent needed to process classified records into the facil ity one year earlierthan they are needed w ould be unwise du e to the rate of technology evolution. Facil ity 2 will have anormal technology refresh in Increment 2.

8/05 11/05 2/0A > r d / ^ ^ S R R ^ p o R I

6 5/06 8/06 11/06 2A37 5/07^ R f i l l P a T ^ R e l 2 P a T ^ P A T ^ O A T

8/07^ l O C

-.fmmpiomttmmmmm^mmmm.F a d l ^ 4 SMct i imPi Dcen

ftmmmt^K^msite ^ A A at e Survey (site 1). Lease AA T J ^ ADesignA A ^ C0frucaon ^

A A jA^ Faciili^ Inspectionjl^cMllfZSalBcBim Braoiaij

FtfM lir Z EM H Out UrooMHlA ~ A Ste Survey (8le 2)

. Lease .Sle #2 AN^TAAA A AFl tOUt .A A A Faclly InspectionERA Increment 1 Deployment Timeline

Source Selection Information - See FAR 2.101 and 3.10CDRL Num ber: 5 - Facil it ies PlanMay 13, 2005 38L O C K H B B O M A B T I < > ^


67/101

^ - -;??^,::sapp?se^>"-'^"- -"' - JflWJI^, , ' ^ P !?W "-;TSiF-W5 *"T"S ^ ^ - ^ ^ ^ B f f : ^ ! ^ f ^ f t ^


Figure 9 - Increment 1 Timeline

1/07 2/07 6/07 8/07 11/07 2/08 5/08 8/08sR2AP-PA A J r i ^ 2 ^ ^ ' " O C ^ P A T /ÔAT ^lOC

x^dll^fp|tcttj|i|igi^|i^fa4ia'|iBBlF^pp%mii lH'^ Stiiiiîirf Prooitr

> l%in|^ûnit Out^racen

SitettG Site Survey (site 3) A A A ^ A A-DesignAA

Construction -A* Fit out .A AA A Facility Inspection

S i te * -2

@unrntSiJte air^Retrflfit PniceMFit out A A Facility Inspection

ERA Increment 2 Deployment Timeline

Figure 10 - Increment 2 TimelineFigures 9 and 10 illustrate that the Facility 1 installation project begins immediately upon award ofIncrement 1, while the facility 2 installation process begins approximately four months later inDecember of 2005. The installation process for Facility 3 will begin in January, 2007 which isapproximately seven months before the end of Increment 1, to accommodate the overall time requiredto install that facility. However, the lease will not be signed until August of2007, the anticipatedbeginning of the Increment 2 contract period. Each facility Installation process is completed throughcertification before operating capability for the applicable facility is achieved.

Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 39L O C K H B B O M A B r I ^


68/101

-T^BjfK-t^frsK'- '^^'T '** '^^' '


4.2 Faci l i t ies Proc esse sThe facilities process provides an orderly step-by-step repeatable way to install, retrofit, and maintainLockheed Martin Team ERA Operational Facilities. They were created by the Lockheed Martin TeamField Operations Manager, and as part of the CDRL 5, Facilities Plan are approved by the LockheedMartin Program Director and ERA PMO through the standard CDRL submission process. The processwill be revised based upon lessons leamed installing ERA Facilities and will be submitted for approvalonce per increment.The facilities process is comprised of three phases: Project planning and control, facility selection, andfacility build out. Project planning and control is a continuous activity with specific tasks for the activitiesinvolved with the installafion, retrofit, and maintenance tasks for each facility.This Facilities Processes Section defines the activities, deliverables, and deliverable frequency of tasksthe Lockheed Martin Team will perform to install, retrofit, certify and maintain ERA facilities. NARAresponsibilities that support those activities will also be described. Each process section will provide ahigh level description of that process to provide context, and two tables listing detailed process steps.The first table w ill list the Lockheed Martin Team activities for the specific facility process. The secondwill provide the NARA responsibilities to support those activities. In general terms, the role of theLockheed Martin Team is to perform the activities to install, retrofit, certify, and maintain facilities underthe oversight and approving authority of NARA. That general rule is true for the facility processes witha few exceptions that w ill be noted within the NARA responsibilities tables.Within the tables we will follow two conventions to save space and make the document easier to read:1. CDRL numbers and names w ill not be repeated in the NARA responsibility tables. The term CDRLwill refer to all CDRLs that are work products for that process step in the Lockheed Martin Teamresponsibilities tab le.2. The acronym PS/SME will be used to refer to the Lockheed Martin Team and NARA Securityexperts who are involved in the Certification and Accreditation (C&A) process to abide by the DCID,NISPOM, and TEMPEST requirements and guidelines. The individual project plan will name thespecific offices and personnel at the time of the project. However, they would include appropriatemembers from contractor and NARA industrial Security Offices (ISO), Designating Authority atNARA, NARA Cognizant Security Authority (CSA), Facility Security Officers (FSO),Communications Security (COMSEC) personnel, and NARA CSA interface with the CentralIntelligence Agency (CIA) Cognizant Security Office (CSO).4.3 Init ia l Fac il i ty Ins tal lat io nInitial facility installation is the work to install an ERA facility. It encompasses three major processsteps: Project planning and control, facility selection, and facility build out Accordingly the initial facilityinstallation processes are organized into three sections, one for each major process step.The initial facility installafion requires that every process step defined in the activities tables will need tobe performed. The Lockheed Martin Team will ensure that all required resources to install a new facilitywill be deployed to the project early in the project life cycle to ensure proper planning, and that will bedemonstrated by the individual process steps presented in the tables. As an example the various

Source Selection Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 40L O C K H B B O M A B T I f i ^


69/101

IWP^^ '^^


70/101

^. , , : f^p^?K^**^ '^" '^v^" ; . - ^E? f r - ' - lg t f s , |p^ - - '^'Tae^wffi^pBiFsipp^*,.


resources from Lockheed Martin Team, NARA and authenticating agencies who will be responsible toCertify a nd Accredit the facil ity w il l be involved in the beginning of the project by providing guidanceand approval of facil ity selection and facil ity engineering d rawings, ancj inspections throughou t theentire life-cycle of the project to mitigate the risk of surprises at the certif ication step at the end of thefacility installation process.4 . 3. 1 P ro j e c t P l a n n i n g and C o n t r o l P r o c e s sAn initial facility in stallation is a large project and aswith all major projects the Planning and Controlprocesses areke y to achieving succe ss. Accordingly each facil ity installation w ill have a dedicatedLockheed Martin Team project manager responsible for installing a single facil ity under the gu idance,direction, and control of the Field Operations Manager, Operation and Support Manager, andLockheed Martin Team Program Director. TheProject Manager will be the Facil ity M anager who w illoperate the facil ity. Each ERA installation shall have a project IPT assigned to the project that will haverepresentatives fro m the ERAPMO, PS/SME, construction prime contractor and sub contractorvendors performing specific tasks, OEM vendors, and all areas of the Lockheed M artin Team. Allfacility project planning andcontrol steps work w ithin the framework of the Lockheed Martin Teammanagement processes as described in CDRL L3 5, Program Management Plan to include operatingunder Earned V alue M anagement.Table 9 presents the process steps the Lockhe ed M artin Team will follow to plan and control an initialfacility installation project. The following narrative explains the content of each column of Table 9. TheActivity number column will be numbered sequentially and is the activity number for the LockheedMartin Team activity. The Activity column lists theactivity. The Work Product column provides theCDRL deliverable, on Non-C DRL work products associated with that activity. The Frequency columndescribes theproduction frequency of the work product.Table 9 - Lockheed Martin Project Planning a nd Control ActivitiesActivity

#1

2

3

ActivityPlan, organize, and control the facility installation,retrofit, and system maintenance related workProvide information and support to programmanagement reviewsProduce input to minutes of Monthly ProgramManagement ReviewsAssess and measure progress

Work ProductCDRL 18, MonthlyStatus ReportsCDRL 17, MonthlyStatus review

CDRL 18, MonthlyStatus ReportsCDRL 22, CostPerformance ReportCDRL 26, EarnedValue ManagementData

Frequency

Source Selection InformationCDRL Number: 5 - Facilities PlanMay 13, 2005See FAR 2.101 and 3.10

41L O C K H B B O M A B T " i ^


71/101

' n i?


72/101

- r ^ ^ - - " ^ - ^ ^ ' -


Act iv i t y#

4

5

6

7

8

Ac t i v i t y

Designate the Facil ity M anager as project IPT Leadto plan, direct, and co ntrol all aspects of the project

Establish a project IPT to perform the tasks of theproject.

This will include PS /SM E, and the nam ing of aconstruction company that specializes in SCIFconstruction.Develop and sub mit CD RL 5 Facil ities Plan that isthe project plan that addresses project objectivesand how they will be accomplished . Include projectorganization, relationships, coordinationrequirements, budget, risk assessment/riskmanagement, roles and responsibil it ies, metricsand reporting.Update the project plan baseline throughout eachstep of the initial facility installation process, or thecurrent facility retrofit and expansion process as theproject progresses throu gh the phases o f facilityselection, facil ity build out, and makes provision forongoing maintenance of facil ity equipment such asUPS, Heating Ventilation Air Conditioning (HVAC),generators, and physical security countermeasures.

Develop and upda te a project schedule to includetasks, timelines, and dependencies. At a minimumdetailed tasks will be included for the followingcategories: management and control, trade studies,facility selection, site surve y, build out, deploy,configure, and certif icafion and accreditationAlso insert scheduled maintenance windows intothe IS throughout the increments.Coordinate and condu ct Facil ity Design R eviews

Work P roduc t

Naming IPT lead andcreation of team

Updates to activity 1and 2 deliverables andFacilities PlanbaselineSigned subcontractwith SCIF specializedconstruction companyCDRL 5, FacilitiesPlan

Integrated Schedule(IS)

Design Review

Frequency

After DownSelect

Within 1month afterDown Select

Within 6months afterDown Select

Weeklythroughoutthe projectwithemphasis oncheckpointactivities

3'" businessday after endof accountingmonth

MonthlySource S election Information - See FAR 2.101 and 3.10CDRL Number: 5 - Facilities PlanMay 13, 2005 42

L O C K H B B O M A B T l ^


73/101

- ,>.,> -fj t^TOW^'-- 'K ^iM':i :jg.l | i i .l^HH I,. I| IJ

Con tract Num ber: NAMA-04-C-0007

Act iv i t y#

9

10

11

12

13

14

Ac t i v i t y

Conduct regular in process reviews

Prepare inputs to h igher level integration and testdocumentation

Prepare input to NARA User training

Deliver training to ERA operations staff and NA RAemployees

Develop, report, and use m etrics indicating thestatus and progress of the deployment activit iesConduct Project IPT status meeting

Work P roduc tDocument

Deployment ReviewDocumentCDRL L31, MasterTest Plan

CDRL L41, TrainingMaterials

Training attendancesheet and completionstatusMetrics to beestablished in activity4 Project PlanMeeting minutesUpdates to FacilitiesPlan baseline

Frequencyaccording toIntegratedScheduleAccording toIntegratedScheduleOnce perIncrementaccording toIntegratedScheduleOnce perfacilityprojectaccording toIntegratedSchedule1 month priorto initialoperatingcapabilityIntegratedinto ac tivities1,2, and 3Weekly

Table 10 - NARA Project Planning and C ontrol Responsibilit ies provide the specific proposedresponsibilit ies o f NAR A in regards to projects to install an ER A facil ity. Timely exe cution of theseresponsibilit ies will facil itate com pliance with the IS. The Activity Num ber colum n will be num beredsequentially and is the activity numbe r for the N ARA responsibil ities. The Responsibil ities column liststhe supported activity from the S ample Lockheed Martin Activit ies Table and the role NARA has insupporting that activity. The Sup ported Activity column contains the activity num ber cross referenced toTable 9 - Lockheed M artin Project Planning and Control Activit ies.Table 10 - NARA P roject Planning and Control Responsibil it ies

Act iv i t y #12

Respons ib i l i t iesMonthly status reports - Review and approve CD RLProgram Management Reviews - NARA will have appropriaterepresentation at the Program Management reviews (participate) and

Suppor tedAct iv i t y12

Source Selection InformationCDRL Num ber: 5 - Facil it ies PlanMay 13, 2005See FAR 2.101 and 3.10

43L O C K H B B O M A B T I N J ^ J ^


74/101

^ ~ ^ ^ ' ' ^ ' ' ' : ^ r ^ -


Act iv i t y #

345678910

Respons ib i l i t iesapprove minutes and CDRL.Assess and me asure progress - Review and approve CDRL 'sProject plan - Review and approve CDRL at checkpoints, and approveSCIF construction sub contractorIntegrated sche dule - Participate in creation through reviewsFacility design reviews - Participate and approve the designIn process reviews - Participate and approve minutesIntegration and test documen tation - Review and approve C DRLTraining Input - Review and approve CDRL 41, Training MaterialsW eek ly Project IPT status meeting - Participate and approve minutes

Suppor tedAct iv i t y35,6789101114

4 .3 .2 F a c i l i t y S e l e c t i o n P ro c e s sThe facil ity selection proces s establishes m uch of the basis for successful deploym ent and suppoprt.Within this step requ irements are gathe red, onsite surveys are cond ucted, and architectural drawingsare created. Active participation of Lockhee d M artin Team facil ity profession als and PS/SM E in thisphase is critical to ensure that facilities that will process classified holdings are suited to cost effectiveimplementation of p hysical security requirem ents. The onsite survey is the most im portant step inselecting a facility that is suited to becom e an ERA facil ity. The following narrative describes the majorfunctions performed in this process step.The facilities site survey allows for a systematic study of real property's suitability to host the enterpriseoperations. Functional, ope rational, and physical security criteria establish the facil ity sea rchparameters for the site survey. Factors of facility preparation time, size, availability of local staff andservices, improvement cost, and fiexibil ity.The assessm ent will identify solution options with pros, cons and financial analysis for each facil ity.Finalist properties m ust be adaptable to the project's stated requiremen ts and criteria. To become acandidate facil ity, a facility mu st show the abil ity to meet or exceed e stablished stand ards ofoperational availabil ity, security, robust cons truction, and other superior pe rformance characteristics.The IPT will review all candidate facil ity survey resu lts, evaluate each report, and va lidate therecomm endations. The IPT will present their recomm endation to the ERA PMO for approval if theassessment assumptions remain valid and new information does not change the analysis and the costmodels. Upon approval the IPT authorize the detailed floor plan design.Architecture and design of the floor space will be perfom ied at end of this step with the actual locationsof all cubes, walls, equipm ent, hard ware, people space, furniture, storage room s, bathrooms, closets,security m easures and any thing that makes up the physical space drawn up on blue prints to bepresented for final approva l to proceed at the B uild Out P rocess checkp oint. The de tailed processsteps for facil ity selection are p resented in Table 11 - Lockheed Martin Facil ity Selection Activities:

CDRL Number: 5May 13, 2005Source Selection InformationFacilities Plan See FAR 2.101 and 3.10 44

L O C K H B B O M A B T I ^


75/101

-^ -."^^W'^^^^^W^"'^'^-^ '.f-^; - ^ ^ ; j . i i * , ^ s ^ j ^ . ^ P ^ , , "

Co ntra ct Num ber: NAMA-04-C-0007

Table 11 - Lockheed M artin Facility Selection Activit iesAct iv i t y

#1

2

3

4

5

6

7

Ac t i v i t yConduct preliminary facil it ies requirements analysisReceive final DD Form 254Receive physical security con solidated levels ofconcern confidentiality, integrity and availabil ityindicatorsStart preparing the Fixed Facil ity Checklist, AnnexA (FFC)Involve the PS/SME

Develop facility-specific requ irements in the form o fsurvey objectives a nd criteria to include facil itymission, availability criteria, functional view ofactivit ies to be perform ed at the facil ity,headcounts, demographics, specific spacecharacteristics, specific secu rity ch aracteristics, andcost driversRequired input is ERA system BOM or assumedhardware configuration to process ERAGain approval at project requirements/project plancheckpointIssue facil ity-specific requirements to GovernmentServices Administration (GSA) and/or commercialreal estate b rokersCreate candidate facil ity l ist from GSA and/orcommercial brokers search results

Review candidate l ist, make recommendation, andselect facil ities to perfo rm site surveys u ponConduct facil ity visits to determ ine ava ilabil ity andsuitability of facilitiesConduct onsite interviews and physical survey toassess facil ity and fac il ity installation requirements

Del iverableUpdates to FacilitiesPlan baseline

Updates to FacilitiesPlan baseline

Updates to FacilitiesPlan baselineUpdates to FacilitiesPlan baseline

Updates to FacilitiesPlan baseline

Updates to FacilitiesPlan baselineUpdates to FacilitiesPlan baseline withfacil ity assessmentreport(s), facil ityfinancial analysis.

FrequencyUpdates tobaselineoccurroutinelyupon changeactivitySubmissionis once perincrementper theIntegratedScheduleAfter DownSelect andupon changeactivity

Once within 1month afterDown SelectOnce uponapproval ofrequirementsand criteriaOnce within 6weeks ofrequirementsapprovalOnce within 3months afterDown SelectAccording toIntegratedScheduleOnce within 4

Source Selection Info

nara tempest

Documents