System for Award Management (SAM)
Presented to: Defense Logistics Agency
September 9, 2011
What’ s the System Landscape Today?
What’ s Wrong with the Current Approach?
Multiple logins îinefficient and confusing
Data overlap among systems îinefficient and creates opportunity for error
Separate hosting, management, and support
Various standards and service level agreements îmay yield varying levels of service
Multiple hosting vendors îmore expensive than consolidated hosting
What Are We Doing to Fix It?
Siloed -Separate systems, each with a separate login
Redundant -Overlapping data
Separate -Various hosting locations, managed separately
How Are We Making the Changes?
Federal Service Desk (FSD)
Current consolidation of Tier 1 help desk services aligns with 1-system approach
Consolidated Hosting Services
One common database in one hosting location means lower operating costs and greater reporting flexibility
SAM Requirements and Operations
IBM is documenting SAM architecture and system requirements and will operate SAM
Requirements will be sent out for bid to increase competition
What Are the Benefits of the New Approach?
Entities (e.g., vendors, grantees)
One login provides access to all the tools needed to register, record reps and certs, and view and respond to opportunities
Streamlined processes decrease the amount of time required to complete a typical registration
Eliminating artificial information category divisions simplifies data entry
One login provides access to all the information needed to make an award determination
Streamlined, integrated processes simplify and reduce the time required to complete an award
Reducing the number of interfaces decreases maintenance challenges and costs
Integrating all data into one database increases reporting flexibility
How Will the New System Be Organized?
IAE system capabilities notionally have been organized around six key functional areas
What Can I Expect from the New System?
SAM is not a portal to existing systems!
Processes were deconstructed and rebuilt without regard for system boundaries
Logical ordering of process steps
Logical grouping of data elements
Elimination of data redundancies
The resulting system, SAM, will include all the capabilities of the legacy systems, presented in a more streamlined, user-friendly way
What’ s Ahead for FedReg?
FedReg will move to the Entity Management functional area within SAM
FedReg is in the first migration group -go live mid-2012
The FedReg registration process will be integrated with legacy CCR registration, so federal agencies do not need to maintain two registrations (in the case where they are also acting as vendors to the government)
FedReg required information will remain largely the same
Existing records will be migrated
SAM will retain the FedReg requirement to pull civilian agency DUNS information from D&B and military service/agencies’ DoDAAC information from DAASC/DLA
Hierarchy will be migrated to a central government hierarchy, based on FPDS
How Will the Hierarchy Migration Work?
How Will SAM Impact Interfaces?
Process Improvements -SAM process-improvement work is identifying ways to reduce the number of interfaces needed
1 Database -As the legacy systems are migrated into SAM, they will be migrating into one database, further reducing the number of interfaces needed
What’ s Changing When?
Legacy system capabilities will move to SAM in phases
What Login Changes Can I Expect?
After migration, all the capabilities in CCR/FedReg, ORCA, and EPLS will be available at SAM.gov -1 login!
Users will be automatically redirected from the legacy systems to SAM
Users will create a new user ID and password -the system will guide them through the process when they log in with their old user name
What’ s Next?
Subject Matter Experts have provided input to and validation of requirements for the CCR/FedReg, ORCA, EPLS migration group
The next migration group includes FBO, eSRS/FSRS and CFDA
How Can I Stay Informed?
Go to sam.gov
Direct any SAM-related questions to [email protected]
Participate in our Contract Writing System/Interfaces meetings, if applicable (write to [email protected] to be invited)