This discussion is going to be about DBIDS throughout Japan -

Defense Biometric Identification System (DBIDS):

I am bringing this issue to light, because recently a friend of mine who is a SOFA sponsored Contractor, he was at Atsugi getting access to the base, where the security guard told him that he wasnt registered in Atsugi's DBID's.  He took a moment and explained, of course he wouldnt be, since he was already registered in Yokosuka's DBID's.

The security guard, then went into saying that the Atsugi Base CO's has announced that "SOON" he will be issuing a mandatory mandate if your not in the Atsugi DBID's he will not grant you access to his installation.

Now, I am very familar with this system, and you can spend a few hours reading about it all through the web. 

One of the issues is how the bases in Japan setup their networks, which is completely different than how Korea did there setup.
------------------------------------------------------------
KOREA BASES STATEMENT FOR DBIDS:

Individuals and vehicles entering USAG-Yongsan are being screened more thoroughly through the Defense Biometric Identification System.

DBIDS links people’s biographic data to their ID card bar codes. Security personnel, using special hand-held scanners, can verify identity and alert security if the card has been reported stolen or the cardholder is wanted by police.

The program’s heart is a centralized and current database of biometric details including a photograph, identifying information such as height and weight, and fingerprints.

Depending on the force-protection level and specific needs, a fingerprint reader can be added to the scanner to match would-be entrants with prints on record.

The system augments what’s collected by the Defense Enrollment Eligibility Reporting System (DEERS/Rapid) with a local address, phone numbers and vehicles or even pets registered to the cardholder.

Those lacking DOD identification cards, including Korean national employees and children under 10, will receive special DBIDS cards with their bar-coded information. Those with common access cards, retiree or dependent IDs can use their ordinary cards.

Children aren’t required to get the cards but doing so provides a form of photo identification and links them to their sponsors, officials said. In emergencies, security officials can use the cards to learn quickly to whom a child belongs. The cards also would keep track of noncombatants being evacuated.

DOD civilians not in the system must show a second form of ID to enter a base; South Korean employees not in the system are barred entry until they register with DBIDS.

The system is encrypted and operated by the same command as the DEERS system, the Defense Manpower Data Center.

How to register

People can register for the DBIDS system at three locations. The registration is mandatory for all personnel assigned to the base (and recommended for those who visit regularly) including servicemembers, civilians, dependents and local nationals.

Servicemembers, retirees and DOD civilians need only their common access card to register; once their sponsor is registered, dependents need a copy of their stationing orders and their family entry approval form.

People can register at three locations:

* Camp Kim's Pass & ID Vehicle Registration Office
* USAG-Yongsan Ration Control Office * ID Card Office

They may register from 8 a.m. to 4 p.m. Mondays through Fridays.

Registration takes just a few minutes.

------------------------------------------------------------
What people need to understand is Korea set this up with a central point server, which allows the entire Korea bases to all sync together.

From what I understand this is going to be a difficult sell in Japan, since everyone has local implementations of servers, and they are not actually sync'd right now.

I dont know exactly how the back-end database is configured, but let me put it into a record analogy for a database.  If they implemented each user, with a specific ID into the CAC database, and they all started at 000001.  Well each base started at the same segment of #'s, which means there are about 16 people out there all having the same segment #.

Even if they decide to figure out a way to sync them and keep them constantly sync'd up, there will be database sync issues over time.  I guarantee it!

My suggestion would of been a centralized server, and all entries get pulled, and sync'd from 1 location, as Korea did.  That was a smart move how they did it.

The only reason why I am bringing this situation to light, is because of my friends recent situation.  I do agree that DBIDS is a great solution, but it must be implemented correctly, or there will be long-term problems, and issues, that you will be having 16 different commands all having their say in.  No one will be the overall implementer.  If they do decide to migrate over to 1 solution, it will be a hell of a time migrating the databases together, but its probably the smartest thing you could do long term.

Locate the server at USFJ - i.e. Yokota since its the central point for U.S. Forces Japan. 

I would hate for local commanders to start banning people not registered in their local DBID's or making someone go into each local security office, and register at each base, while you shouldnt have to.  It should automatically sync together, or pull from a centralized source.

Here are some links for resources:

Kadena switching to DBIDS base access system
http://www.stripes.com/news/pacific/okinawa/kadena-switching-to-dbids-base-access-system-1.112530

Misawa to implement DBIDS security system
http://www.stripes.com/news/misawa-to-implement-dbids-security-system-1.87877

60,000 must register to continue accessing Kadena
http://www.kadena.af.mil/news/story.asp?id=123215045

DBIDS nears registration deadline
http://www.dvidshub.net/news/63903/dbids-nears-registration-deadline

Grats Adam! A thread that breaks my lurking streak... I've been on the wrong side of this before, here at Yokota. For some reason, the data in the DBIDS system was different than what was on my ID card. The gate guard hassled me and forced me to drive all the way around the base, to enter the only gate that has a laptop to update DBIDS info.

Then, the guy who could do it was on break... I had to wait around for almost an hour for this guy. Finally, I get it updated and as I'm trying to go through the gate again, it squawks... and before the gate guard could say anything - I was like "I JUST came from the DBIDS guy!"

At that point, he let me though - apparently they're aware of a small time delay between getting the system updated and their hand-helds. Guess it's not a real-time sync, eh?

You would think that DOD would already imprint this information on the ID or linked to some DEERS data base that could be checked Japan wide so that there is no need for people to register a card at every base. So if I want to spend the weekend at New Sanno I do not have to get there before 4 pm to register in dbids.

Woo-hoo! More places to fill out paperwork.

So if I want to try out the Atsugi golf course, I will be denied entry because I'm not in their DBIDS? I was under the impression that with my DoD issued ID card I can access ANY DoD installation (barring Area 51 and other TS sites). ;-)

I'd have to check the applicable instructions to see if he can deny access based on DBIDS... I know the CO can bar someone from the base if they cause problems (same as barring someone from the NEX for shoplifting), or in the event of increased THREATCON; but no access if you're not assigned to the base and not in their DBIDS? Sounds like someone is overstepping.

DBIDS is a good idea. Many local commands use something very similar. The Navy Region that I was stationed at before here used a similar system, but issued a badge to everyone in the area. Every local command had a say in the badge approval process. While that did make the process tedious, I almost never had to use my ID card for seven years. If every installation used the Common Access Cards the way they were designed to be used then incidents like Chaddeus described would not happen anywhere there was a DoD installation.

Adam, good write-up. Here is some more info for everyone.

Adam is correct that Korea (USFK) is network configured different than Japan currently is. Understand that DBIDS, originally called BIDS, was developed by DMDC specifically for USFK at the request of the USFK commander (that was back in 1998).

Being a top-down managed program there was needless to say very little whining by installations who may not have wanted to play ball... the 4-star was the boss.

This of course led to a Korea-wide managed program to include, you guessed it, network connectivity. This is why DBIDS (BIDS) was designed as a central server run system, for Korea who planned on operating in this mode.

In this respect Korea was unique. All bases, all services; Army, Air Force, Navy, Marines all working in harmony (so to speak) operating under a single ops plan or regulation Korea-wide... a commanders dream.

As the years went on and more commands around the world learned of and wanted the system this bliss proved to be unique to Korea.

Germany was next up with BIDS circa 2002, although the Army had some sort of biological something system with the same BIDS acronym over there so they couldn't call it BIDS. They called it IACS, Installation Access Control System.

Next up was a few sites around the DMDC West Coast HQ in Monterey CA who implemented BIDS.  With all these non-Korea sites now in play the system added on Defense to the term thus DBIDS.

Besides the name game came network issues with all these other areas, or more specifically the inability for everyone within a region to play nice together as they had in Korea, which put a wrinkle in the central-server process.

Japan, 2004, Yokosuka… first up in Japan with DBIDS and in reality the only potential player expected to go down the DBIDS road. The plan? Yokosuka, CNFJ HQ, the central server location for all CNFJ sites; Atsugi, Sasebo, Negishi, Ikego, Urago, Fuel Farms would all feed into that central site as Korea does to their central site. Bliss for the Navy in Japan… until ONE-Net made it all barf and failed to certify DBIDS for the Navy in a timely manner, timely as in still not! This left Yokosuka alone with the system.

Not long ago Atsugi became another ‘loner’ since they couldn’t talk to Yokosuka BUT still wanted the system. And of course since even the Navy sites can’t reach out to each other, they surely couldn’t get to Yokota AB.

2006, Yokota AB, DBIDS implemented partially and then fully in 2008.  The plan?  Central server location for USFJ sites, which could include the Navy if they could reach there... they can't (yet).

2009, Misawa AB joins up and links to the USFJ central server.

July 2010, Kadena AB Okinawa joins up also links to the USFK server.

The theme for Japan has been network related roadblocks to a Korea-like shared operation.  If those roadblocks with the Navy network could be worked out then those stand-alone sites in the Navy could be, and would be, easily merged with the USFJ servers... the DB plan has already been developed and is just waiting in the wings.

USARJ is also eagerly waiting to implement DBIDS, although they still haven't found any money for it.  But they too, any and all USARJ sites would also feed into the USFJ servers.

So, for all of you at Yokosuka , Atsugi and Sasebo (soon) I'm sorry to say you will have to maintain registration at numerous sites, at least for awhile.

Sorry for the book...